Hi, I was not able to create an account on sourceforge and therefore was not able to create a bug report. Maybe someone of you with more patience or an already existing sourceforge account can create the report.
I am using enigmail 1.8.2 on Thunderbird 38.4.0 on Linux (Archlinux). After the Update from gnupg 2.1.9 to 2.1.10 enigmail does not encrypt mails anymore. I have two keys. An old one that is expired and revoked (E4835646BDE8EA81) and a current one (E72581B1FE9F104C). I keep the old key to decrypt old mails. nigmail tries to use the following command: /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch \ --no-tty --status-fd 2 -a -t --encrypt --sign --trust-model always \ --encrypt-to <[email protected]> -r 0x5334752442830117 \ -u <[email protected]> --use-agent This command works with gnupg 2.1.9 but not with gnupg 2.1.10. You can test this easily with the command gpg --encrypt --encrypt-to [email protected] -r 0x5334752442830117 --armour Gnupg 2.1.10 gpg gives the following message: gpg: key specification '[email protected]' is ambiguous gpg: (check argument of option '--encrypt-to') gpg: '[email protected]' matches at least: gpg: B953A7355F1149ABCA8F2B2AE4835646BDE8EA81 gpg: 6D3A9AB887A6229308D9C007E72581B1FE9F104C The announcement of gnupg 2.1.10 says: * gpg: Check for ambigious or non-matching key specification in the config file or given to --encrypt-to. https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000381.html So it seems this bug is a new "feature" of gnupg 2.1.10. It can probably be fixed by using the new option --encrypt-to-default-key instead of --encrypt-to. Oskar Hahn
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
