On 12/24/2012 08:24 AM, Olav Seyfarth wrote:
[snip]
>> I can check the box manually to sign and to encrypt, and then it works just
>> fine. But it will not remember my pass-phrase.
> 
> Different story. For ENcryption, no passphrase is required. For signing, the
> passphrase of the (hopefully protected) private key is required. For 
> DEcrypting
> the passphrase of the private key that the message is decrypted to is 
> required.
> 
> GnuPG 2.0 / gpg-agent caches passphrases for signing separately from those for
> decryption (which IS a good idea). So If you start afresh, sign and encrypt a
> message (sign with and encrypt just to your own key "A"), upon opening that 
> same
> message, you get prompted for the passphrase for DEcryption for "A". That is 
> as
> it is designed to be. Whether and how long these passphrases shall be cached 
> by
> gpg-agend is set in gpg-agent.conf in your GnuPG profile directory, see
> 
> http://www.gnupg.org/documentation/manuals/gnupg/Agent-Options.html
> (search for "cache" within)
> 
> Olav

None of that worked. Much private e-mail with Olav, and rummaging around
the web for days and the result was:

> I think I solved the problem. I found some undocumented code on the
> Internet that did not work, but could be fixed.
> 
> I put this in my .xsession file (at the end)
> 
> SOCKET=S.gpg-agent
> PIDOF=`pidof gpg-agent`
> RETVAL=$?
> 
> eval $(gpg-agent --daemon)
> GPG_SOCKET_FILE=`find /tmp/gpg-* -name $SOCKET`
> echo "Updating socket file link."
> ln -s $GPG_SOCKET_FILE $HOME/.gnupg/S.gpg-agent
> 
> ORIGINALLY, I had only the line
> 
> eval $(gpg-agent --daemon)
> 
> in there as specified in the documentation.
> Trouble is that the eval leaves the S.gpg-agent socket up in
> /tmp/gpg-UGLYname directory instead of my .gnupg directory. I cannot
> even move that socket or copy it because of permissions, but it turns
> out I could link it.
> 

_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to