What for? Multiple GB's of almost-known plaintext encrypted under a single key just makes it easier for an attacker. You should only encrypt what's secret. Your /usr surely isn't!
Aren't you thinking of the old times cryptos where one could use frequency analysis of the characters used in the encrypted text and then put up a table and compare to the apropriate language character frequency to find out what each character most probably would represent? In that case more data will make the analyse easier.
But in todays cryptos as far as I know (I may be wrong here) the more data you have doesn't make it easier to decrypt the content.
Best regards,
Jonap
Marc
- -- In July, [...] the FBI arrested a Russian computer security researcher who had presented a paper on the strengths and weaknesses of software used to protect electronic books. Dmitry Sklyarov [...] landed in jail because the Digital Millennium Copyright Act (DMCA) makes publishing critical research on this technology a more serious offense than publishing nuclear weapon designs. -- Bruce Schneier, Crypto-Gram Aug 2001 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE7vgz+3oWD+L2/6DgRAnlaAJ4tVONQArSzX3eTNEl8KvYyDTFZMACgwDoi rmlUkPMM8EAF6BgxUc3PvCA= =mvHE -----END PGP SIGNATURE-----
Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
_________________________________________________________________ Hämta MSN Explorer kostnadsfritt på http://explorer.msn.se
Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
