Question re use of dd to overwrite asset in README

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just me with another question ...

Is there any particular reason(s) the examples in the
loop-aes README use "dd" to overwrite the device with
encrypted zeros (in order to mask how much cyphertext
is subsequently written there), instead of (say) using
shred eg..

	>~ ln -s /dev/fd0 tmp.$$
	>~ shred -n 1 -v tmp.$$
rm -f tmp.$$

- as can be seen in some of the older online guides to
loop-aes.

Why do I care? Because dd doesn't appear to have
usable exit values (it's 1 no matter what happens?),
so you can't really test in a script if it's  finished
properly.

On the other hand, shred has a non-zero exit value if
something went wrong.


		
__________________________________ 
Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 
http://discover.yahoo.com/weekend.html 


-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux