Quit fucking around on Slashdot and hire a hardware designer. It doesn't even have to be an EE. Right now hobbyists are going from idea to product without any formal training.

Hack a Day asked cold boot team member Jacob Appelbaum what he thought of the approach.

Here's Jake's unedited response:

Yeah, it's not a solution. It simply seeks to make it more obscure but an attacker would certainly still be able to pull off the attack.

From what is on that blog, there's still a full keyschedule in memory at this time. This is how we reconstruct the key, the redundant information in memory; it's not just the 128/256 bit key itself. For older methods, they needed the actual specific key bits but we don't need them because we recreate them.

Basically, the CPU is acting as a ghetto crypto co-processer. Emphasis on ghetto. It's a nice suggestion but the devil is in the details and sadly the details in this case aren't really up to snuff. It's a bogus solution.

I've always been a big fan of Sprite_tm's projects. http://hackaday.com/search/?q=sprite_tm