Signing vs. encrypting was: Cipher v public key.
ama at inmedias.it
Wed May 31 11:31:14 CEST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Laurent Jumet schrieb:
> When sending a message like this one, signed, compressed but not
> is there anything that goes bad, in security terms?
> This is to avoid problems with line lenghth and charsets through internet
In security terms, lots of things can go bad when sending anything
through the internet ;-)
Encrypting protects against unauthorised reading of the plaintext, but
not from manipulating the encrypted data. Signing protects against
manipulation of the data, but not against unauthorised reading of the
plaintext. (In fact it does not avoid the manipulation itself, but you
are able to detect, that the data has been manipulated).
Signing and encrypting are two totally different things (not to mention
compressing). So if you want "save" transmissions you have to do both,
signing and encrypting!
Problems with line length and charset shouldn't occur during the
transmission of your mails, because Mail Transport Agents don't take
care of the mailbody (and the headers are not signed or encrypted). What
exactly do you want?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Gnupg-users