sign encrypted emails

Hauke Laging mailinglisten at
Sun Jan 5 17:07:08 CET 2014

Am So 05.01.2014, 10:15:51 schrieb Robert J. Hansen:

> Your problem can be solved trivially by establishing a policy of,
> "Encrypted messages must contain a notification within the signed
> message body of who the message is encrypted for."

That is neither trivial nor reliable nor the best approach to deliver 
this information.

> For many users this sort of policy is a good idea.  For the majority
> of users it's overkill.

Like verifying fingerprints? 8-)

> Why do you want a policy decision to be
> permanently enshrined in GnuPG's mechanism?

As I said in my first mail in this thread this isn't about changing 
GnuPG at all because 

a) this problem is one level above GnuPG

b) GnuPG already has all the capabilities necessary to do this.

As I also said the reason why I have asked this here is the availability 
of people who can make useful comments on that (and are probably 
interested in such general discussions).

Crypto für alle:
OpenPGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 572 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20140105/232df8d5/attachment.sig>

More information about the Gnupg-users mailing list