full-disclosure - Gutmann's research paper today

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8e5ffb560602081003m33e9d5d3h7ff9080cb51c6054@mail.gmail.com>
Date: Wed Feb  8 18:03:34 2006
From: gautam.bipin at gmail.com (Bipin Gautam)
Subject: Gutmann's research paper today

but guys the old 'Gutmann's research paper' doesn't properly clearify
a PRACTICAL way to sanatise the RAM. Ya ofcource, without physically
destroying it.

(anyone? who good idea on this topic???)

say; i have to sanatize my 512mb RAM. Which would be more better to
implement in immidiate emergency?

a). within the next 5 minutes completely overwrite my RAM (say) 5 x 60
= 300 times with a bootable media after reboot.
                                                 or
b). With a bootable media after reboot do some complete random wipes
first. Hold the memory like that for next 10 minutes and repeat this
same process several times.

Feel free to point me to some kernel modules (if any?) that can be
used to transperently encrypt the I/O of RAM once system boots up and
basic drivers are loded.

I need some recomendations on 'proper' RAM sanitization!
-bipin