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
| ||
|
Message-ID: <AANLkTikyBsG7lnIqAy5dwgb4-iVRLeYGHTy-diKblvCM@mail.gmail.com> Date: Wed, 26 May 2010 10:15:32 +0545 From: Bipin Gautam <bipin.gautam@...il.com> To: Marsh Ray <marsh@...endedsubset.com> Cc: full-disclosure <full-disclosure@...ts.grok.org.uk>, Valdis.Kletnieks@...edu Subject: Re: Stealthier Internet access > it's a *bad* sector, so reading and recovering the data is a bitch... No, storing in Negative Disk, bad sector, stenography, slack space are all bad places to store data! In short, Flash memory may require multiple wipes before data is securely deleted because many of them use uses wear-levelling algorithm. http://en.wikipedia.org/wiki/Flash_memory Because of the particular characteristics of flash memory, it is best used with either a controller to perform wear-levelling and error correction or specifically designed flash file systems, which spread writes over the media and deal with the long erase times of NOR flash blocks[citation needed]. The basic concept behind flash file systems is: When the flash store is to be updated, the file system will write a new copy of the changed data to a fresh block, remap the file pointers, then erase the old block later when it has time. _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists