-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12.12.15 05:53, Oskar Hahn wrote:
> * 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.
man gpg2 says:
- --encrypt-to-default-key
If the default secret key is taken from --default-key, then also
encrypt to that key.
I.e. --encrypt-to-default-key would only work if you specified a
default key in your gpg.conf file.
- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWa+p2AAoJENsRh7ndX2k7ZBIQAKl5VPMcHCWMFVCDnhlEWTEL
SM9m1OBTCAn1AuQacWoyo1SUNbLc/NsxF4G/fiAc431PD5ByqY5KhrxE051zbPke
DXBtrru4rznZoiQMNf0VSJnFhTZpf6km0Ew1Fpdrd7lKqPxUGkSJWkCmaqrHVUmo
QkNUp6VdfFXzSyXiT7RQFh/ecRRFfOqZOk+OT7qgidc5rDXx2BM+o9cs+S2w68+C
xu64BkIrHCEZetxkbxr75AifNyFGKGmJ72BGySDXu61UaSEoZOY93UpvSdNm0lHf
V3rro34dqg2MiSRZKz2EicFKxPf/g5oA524aFIoQnIZqgPUa0Kz2y/JXVZa7rD0c
1trgn+nRl6Xzd6dP03mqq0FkmiPjY389jovuHGHdvb8YAlkKoBLI6L4U5p1Vnop0
Y5vh1aVX6/R060Es7En3RG8z2nFM2v+tLDb8gb/xjkOtZfnOvUVHuhZGo+LwDUqE
9joe1xRAqmtIPP1d3VXcX8oizGuYMP25gxV0ztTwXzop3FyOe9gHtZVDkXUZf+ZA
BWL5XYUO7+zMb7XLNsSgCCrW3wKnQRFHudIxwrzG885EIBsA04ar03sh546EpE3q
AO3J+8x3PptclmDDv6jibOVXoqzjetZfFNPOs/J9NFBRpr9AlN06TGSNbFSlnHN2
VgznsFprv2N2VV5vOb5M
=5xmq
-----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
