> > Actually, it's all-bits-zero, all-bits-one, all-bits-zero. This prevents
> > people from reading the previous data from residual magnetic fields underneath
> > a disk which has simply been wiped with zeroes, etc. The complete cycle for
> > each bit is enough to minimize this risk.
>
> Hmmm I guess we need a /dev/one? (Actually not a bad thing to have)
IMHO the name /dev/one would be a bad idea. Becouse this could mean an
integer one which is 00000001 for 8-bit, 0000000000000001 for 16-bit, and
so on.
I don't know a better name - but IMHO /dev/one would be a bad name.
BTW: I think a good crypto filesystem is allways better than secure
deletion, becouse with a crypto filesystem (i.e. crypto-loopback) you
don't need to 'destroy' the data to make it useless for someone else.
greetings,
- clifford
-- -- -- -- -- -- -- -- -- -- -- -- --
Clifford Wolf (CEO and CTO)
The ROCK Projects Workgoup IRC: IRCnet / clifford
http://www.rock-projects.com/ http://www.clifford.at/
e-mail: c.wolf@rock-projects.com email: god@clifford.at
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/