Bonjour,
[quote]It is important to note that TrueCrypt is disk encryption software, which encrypts only disks, not RAM (memory).
Keep in mind that most programs do not clear the memory area (buffers) in which they store unencrypted (portions of) files they load from a TrueCrypt volume. This means that after you exit such a program, unencrypted data it worked with may remain in memory (RAM) until the computer is turned off (and, according to some researchers, even for some time after the power is turned off*). Also note that if you open a file stored on a TrueCrypt volume, for example, in a text editor and then force dismount on the TrueCrypt volume, then the file will remain unencrypted in the area of memory (RAM) used by (allocated to) the text editor. This applies to forced auto-dismount too. [/quote]
secure.wikimedia.org/wikipedia/ … oot_attack
Plus de détails: tails.boum.org/contribute/desig … y_erasure/
Voila pourquoi.
J’ai déja trouvé la solution pour effacer la RAM de la meilleur façon qu’il soit à l’extincition/reboot de l’OS:
[quote] * An initscript used to start kexec at the end of the shutdown process
* A Hook to initramfs to include sdmem, and a script to be included in this initramfs. This script is controlled by options defined in a Debian /etc/default file.
So the process is quite simple. At the end of the shutdown process, the last initscript that is executed is the tails-kexec one, which executes a kexec passing the right options to the “sdmemed” initramfs.
The use of this kexec trick is the only we’ve found to be sure to wipe all the non-kernel ram memory. Otherwise it’s quite complicates to know how much userland memory has to be wiped.[/quote]
Par contre je ne sais pas comment mettre cela en oeuvre sous debian, je n’ai pas les connaissances/compétences, mais ca semble être très simple pour quelqu’un qui s’y connait un mimimum… donc si quelqu’un pouvait m’expliquer comment faire ce serait sympa et ca profiterais à beaucoup d’entre nous! 