Ok, that makes sense. I was using pinentry-ncurses. I was adding the password for keys using keychain->gpg-agent->pinentry-ncurses before starting TB.
So after installing pinentry-gtk2, and editing ~.gnupg/gpg-agent.conf to contain "pinentry-program /usr/bin/pinentry-gtk-2" TB/enigmail now opens the pinentry-gtk-2 dialog to receive passwords. So this works fine now but it is worth noting that my expectation was that if I preloaded passphrases using keychain which in turn calls pinentry-gtk2 those keys would be available to Enigmail/thunderbird. This is not the case as Enigmail seems to need to authenticate passwords again once TB is opened. On 01/28/2013 06:37 PM, Anthony Papillion wrote: > On 01/28/2013 03:43 PM, soportek wrote: >> What is the correct use of gpg-agent with Engmail and TB? >> >> Currently I am starting gpg-agent daemon in my .xinitrc script and >> adding keys to memory with keychain. >> >> I have activated the gpg-agent checkbox in the Enigmail preferences but >> gpg-agent keys do not seem to be available to Enigmail. > > Have you also made sure that either pinentry-gtk or pinentry-kde is > installed? I had agent working fine but it wouldn't connect with > Enigmail until I installed (in my case) pinentry-gtk. This is the dialog > that asks you for your passphrase. > > Anthony > > > > _______________________________________________ > enigmail-users mailing list > [email protected] > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
