-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thursday 06 August 2015 02:14 AM, Daniel Kahn Gillmor wrote: >> enigmail cannot decrypt/encrypt and sign messages with gpg 2.1.6 >> in experimental. Reporting early so that we can fix it before it >> enters unstable. > > hm, it works for me with enigmail 2:1.8.2-3 and gnupg 2.1.6-1. Is > it possible that you've got some odd combination of > pinentry/gpg-agent/desktop-environment or something?
I have gnome 3 and the same combination works when I downgrade to 2.0.38-3 from unstable and restart. > dpkg -l 'pinentry*' 'gnupg*' gcr > $ dpkg -l 'pinentry*' 'gnupg*' gcr Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=========================-=================-=================-====== ================================================== ii gcr 3.12.2-1 amd64 GNOME crypto services (daemon and tools) ii gnupg 1.4.19-3 amd64 GNU privacy guard - a free PGP replacement ii gnupg-agent 2.0.28-3 amd64 GNU privacy guard - password agent ii gnupg-curl 1.4.18-2 amd64 GNU privacy guard - a free PGP replacement (cURL) un gnupg-doc <none> <none> (no description available) ii gnupg2 2.0.28-3 amd64 GNU privacy guard - a free PGP replacement (new v2.x) un pinentry <none> <none> (no description available) ii pinentry-curses 0.8.3-2 amd64 curses-based PIN or pass-phrase entry dialog for GnuPG un pinentry-doc <none> <none> (no description available) ii pinentry-gnome3 0.9.5-2 amd64 GNOME 3 PIN or pass-phrase entry dialog for GnuPG ii pinentry-gtk2 0.8.3-2 amd64 GTK+-2-based PIN or pass-phrase entry dialog for GnuPG un pinentry-qt4 <none> <none> (no description available) un pinentry-x11 <none> <none> (no description available) > Are you able to encrypt/decrypt/sign from the gpg command line? everything works with gnupg2 2.0.38-3 from unstable. It looks my gcr is old, I'll try updating gcr. > also: decrypt and sign are secret key operations, which would > implicate the agent (and possibly pinentry). But it looks like > you're suggesting that encrypting is also broken, which is a public > key operation. > > Feel free to try sending me an encrypted, unsigned mail personally > (key fingerprint 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9) if you > want to test the public-key-only operations with enigmail. > > hope to help get this sorted out, > > --dkg > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVwt/gAAoJEM4fnGdFEsIqWjYP+gLNvAd5yIon5MyfsXyAdSD+ 4f3uPJ5ifxuhRZz5DDrtTM6UHSpao4kltHE2FL4I7MBd0CWIMHl0/fC2zn7jEcuF RvXyXWXeh6/tU+DyOiP8x4t3dSgK/H0VZanLsSupztWBYd+EsC1OjHMqfa3NN/3w /nAovweeOGMxA662+ZqW2hXDdoRtQakr9lnCq1RAyY+638/sndzTWWGMLt0O2/M6 0bjyMixrk9raDTMxbwuDOJ/SJGvWozRLYZG/zhecMDVODuFQeJfSNi1HvLdBWRhM FV6G3+0OdbkLqkkRuP/LU4ms4V5W8ABvyr11XL1FztjcINRRlgY5yS+RK07rxss7 PO8+btAP9OjVPDKR1sVqhKNbk9uHF7PtQZ5XbXxhe674s4wznMnLzpfxoWTUHaDf eZvAeGTzWSOD41v94wohRs+xGhjquFz6yw4E0lAcurhRhTZxjdU2gLJP06TrYkR0 kb6SLqKRrNnRuntEzIcJKWzMWd++cH4VDo90EfXR0AhoiplGt7PREFqHUTFo1lpH 10SEt+CZzYtdTb0+PU6c3PmubxKZYsk8C8SEtngwAYnc4qTyvg/bciuoPqI4Qs4C Ip9G8RT71JMun/phsedO4sB7IPGHSitx39kfVBd4x+SidN+9hlJe4VzqDD9TiFpI +y2yulxmWRbmvQiE5Ya7 =6o89 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org