Package: gnupg Version: 1.4.2-2 Priority: wishlist There are some MUAs (like mutt) that do not encrypt mails you send with your own key, which makes them unreadable to you once stored in a folder. Since this issue can be prevented by the use of the 'encrypt-to' option in GnuPG it would be nice if the default skeleton file for gnupg documented it a bit more.
Attached is a patched changing the skeleton file to help those that don't want too dig to hard to find a solution to the problem above. Regards Javier
diff -Nru gnupg-1.4.2/g10/options.skel gnupg-1.4.2.new/g10/options.skel --- gnupg-1.4.2/g10/options.skel 2005-05-31 08:29:58.000000000 +0200 +++ gnupg-1.4.2.new/g10/options.skel 2005-10-28 18:22:44.000000000 +0200 @@ -39,6 +39,12 @@ #default-recipient some-user-id #default-recipient-self +# Use --encrypt-to to always encrypt to a given gpg key. +# This is useful, for example, when sending mail through a mail client +# that will not automatically encrypt mail to your key. Thus, preventing you +# from reading encrypted mail you've sent to others and stored a copy of. +# encrypt-to KeyID + # By default GnuPG creates version 3 signatures for data files. This # is not strictly OpenPGP compliant but PGP 6 and most versions of PGP # 7 require them. To disable this behavior, you may use this option
signature.asc
Description: Digital signature
