-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12.12.15 05:53, Oskar Hahn wrote:
> 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.

This problem cannot be solved by Enigmail, but needs to be fixed by
yourself. You seem to have more than one key using the same email
address, which is ambiguous, and which GnuPG should not have accepted
for a long time.

The correct solution is to explicitly select a key in the account
settings (Edit > Account Settings > OpenPGP Security --> Select Key).

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWa+efAAoJENsRh7ndX2k7W8oP/3I6PSQ0Q0EeT/TZyApYx+vX
2dR8atyZ+NdRfAQ2Cd4N/BJ6o8jkEVYmF153jNfW5RWqZOk+6Tu8HA2pj6oSiv2x
1U/aStSyggHjYxoAL1kfq1DmgfBFoHgHzIrQw6/Y74ystYk4pZTlp9aTFrXqo7VN
ZGHSn6fdoAYp4o8hg+LLvAnBl07M+u3DjzHGQOR8tgHNdW5Cv4spTq4z22Gy19+s
xTCS6FFh0n/Pf4WnRhnbuLFtUcyNMYd74MxsnNOVOgIA5cbvtPcRF3veRKmtwsb7
NjjepGWwnc89kkTAh5hy87wK9ECoZCAu/0nz+OpjxdMrE4I3U7VkF7vyTbr6K+z7
Kj4ipA6YoNA38nDD9LtBozko2HVBfADqnVKzBasNl9RAFFgIaWNJbokHL0J7KW8y
Cfw6J0Cm7CR9GqNgjg1Ljx8wqs1Ffvw3CnXGtU880UiJBT575awzwIG7FSCfu9I+
P7qX8ltvzdMLarh6W1PIEdLCKTE2lP3RXHBB03pUUxJyv874LicjR/uQXAO8tizO
F5drkJLR0nGDbyx23uu2DFU/gepG52fyghixapwcRlG0GUVlTvQLMdB7HdphFXp1
QnrDj6iMd7vldrBptXLnv14UxsgtZp58AdZJ2GOxPi1MT3b+DVu2DGlQ54waJCML
brDU6+zzgBdR5q2LH3FI
=eRTA
-----END PGP 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

Reply via email to