<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mjg59</author><text>This is mitigated by a Trusted Computing Group feature - at boot, the OS sets a non-volatile flag, and clears it again on clean shutdown after wiping any sensitive material from RAM. If the system boots with the flag set then the firmware wipes the RAM before booting anything. This doesn&amp;#x27;t protect you against someone pulling the RAM out of the system and dumping it there, but that&amp;#x27;s a much harder attack.</text><parent_chain></parent_chain></comment><story><title>Show HN: Simple demo of a cold boot attack using a Raspberry Pi</title><url>https://github.com/anfractuosity/ramrecovery</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>oskarw85</author><text>It&amp;#x27;s nice to recover an image but encryption keys are not that. One bit flip and it&amp;#x27;s game over. This experiment is more useful for human-readable document forensics than anything else.</text><parent_chain></parent_chain></comment><story><title>Show HN: Simple demo of a cold boot attack using a Raspberry Pi</title><url>https://github.com/anfractuosity/ramrecovery</url></story>