-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 14.08.14 13:41, Jogi Hofmüller wrote: > Dear all, > > After a recent upgrade to enigmail 1.7 (Debian/testing) I got > annoyed by the "gnome hijacked gpg-agent message" and disabled the > gpg part of gnome keyring. Now enigmail asks for my passphrase > every time I read an encrypted mail and even twice when I send one, > despite telling it that it should keep the passphrase in memory.
Why? You should only get the message when you save the Enigmail prefrences. > What's so bad about gnome keyring that all of a sudden enigmail > doesn't want to work with it anymore? It worked fine until 1.7 > appeared. How are others handling this? The "only" problem is that Enigmail cannot configure gnome-keyring, i.e. when you change the passphrase caching settings, Enigmail cannot reconfigure gnome-keyring (which works in gpg-agent). > Personally I would say that PGP is complicated enough and the new > behavior of enigmail doesn't really make things easier ... Why don't you set up gpg-agent or re-activate gnome-keyring for gpg? - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEVAwUBU+zSqsk25cDiHiw+AQgADQf/aHgaXzIyfW716riWCtDGzNNcJyq0b7Ud TMUgYTMIQy7GTv2x5Ko9AgJw9X/V5AeAErlXOABVcJ2zOVPVkABRjW7FVPYECoFy NXyKRgftNabsqSuqcoZFYakyP0WQ3s65BIx5cfBsLUrZGIlqNypL8hvS7eq2Gx8Y YSziJZhsxa6qYyXgGF0Nk6RmHkbaXJSvj/Gc/xwHZywUAWVAG8mO8jLHFZjehF+z ySUKXdcxZbor2pConAlPAfJQgGRJDTLtVwLy5MkW3rIBfjjxZ/KlJ2ifA8pShzXL ICRVrLVC5zmElokv8aKIB7H3f/het/dOQBIMs4EzDG9t381LEpWO0w== =uuRu -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
