Liquid Air or clean H2O (destillata) will work...
But thank you!!! espcially for your interests... I think you should get +Rep
@ chipsy: Yeah, I think you've understood it well!!
PC A using SDRAM
PC B " DDR
PC C " DDR
PC D DDR2
PC E DDR2
PC F DDR2
It goes on to say that newer memory technologies decay data at a faster rate but that even the shorter times are enough to facilitate most attacks
Thanks to Princeton University, EFF and Wind River Systems for making this info available in 2008.
You already got a very minimal Linux at your hands in the form of kboot / petitboot. You can drop into a shell from the bootloader, mount your HDD, load the exploit module from there and dump the system memory to it.
I don't know if it's possible to use the RSX memory - it would definately involve some serious kernel hacking. The current implementation of ps3vram uses it as a block device rather than "real" memory. If it were possible to use it as system memory I'm sure someone would have implemented it already because wasting ~200 MiB of perfectly good memory would be pretty stupid, wouldn't it?
As for the argument of "software reboot" vs. "cold boot": you want to avoid the OS to clean up after itself on reboot. It won't clear all of memory (that would make reboots awfully slow) but it definately will destroy some of it's more important data structures, stop processes etc etc. With a hard power-off you avoid that and ensure that the RAM contents represent the state of a fully operational system.
From my limited knowledge of this form of side channel attack it would have to go down like this (your PS3 would have to be disassembled):
1. Prepare kernel modules so they can be used from kboot / petitboot shell
2. Write a script to do the module loading / dumping so you can do it fast
3. Boot into GameOS and set the default OS to OtherOS - do not select automatical reboot
4. Spray liquid air or nitrogen on your memory
5. Yank the power cord
6. Keep applying coolant
7. Power on the PS3 booting into the bootloader shell
8. Start dumping process
One alternative would be to dump the system memory to RSX memory instead of disk since writes to RSX memory are a lot faster than writes to disk. This would help in saving the memory contents as fast as possible but would also require a working ps3vram module within your kboot / petitboot environment. Once the system RAM has been stored in RSX memory you can write it to disk from there without a hurry.
If the footprint of a small linux cannot be shrinked further, i think it still can map to other parts of the mem, so after multiple dump/multiple allocation near complete dump can be done...
Did anyone ask Mathieulh? because he did already dump lvl2. I think he will not share his dump but he can give the right direction...
But after dumping a big part of the RAM, the PS3 could still get really hacked... That little part doesn't matter much. As I said a linux which uses VRAM/HDD/whatever but RAM/... instead of the XDR-RAM, will be just great!!!
@tridentsx: A hard poweroff won't clear the RAM, if you keep the RAM at a very low temperature (-50°C)...
before with the lv0/lv1 dumps he didn't do himself) to "do it yourself" so he definitely has no intention of helping others dump their own.
Mathieulh did, however, tell CJPC they plan to post some information dragged out slowly over the course of several months (extending their "bragging period" in attempt to make themselves feel important) so this is why many PS3 Devs are now sitting back and letting them do all the work, as it appears that is the way GeoHot and Mathieulh want it.
To anyone still wishing to pursue GeoHot's coldboot ramblings, I suggest you read einzwei's thread as it seems he's one of few able to see through them.
One method to strip linux to its bare minimum would be to build a kernel that only contains the modules necessary for the dumping process (no bluetooth, networking etc) and put the dumping software into the initrd to run as the init process. This could be combined into a single image (like kboot / petitboot already does) and stored in flash instead of kboot / petitboot. It would then have to write the dump to an USB attached disk containing for example an ext3 partition.