On 12/15/2014 05:39 PM, outa wrote: > $ echo $GPG_AGENT_INFO > /run/user/1000/keyring-BUeGSx/gpg:0:1
I'm a little surprised by this, since i don't think this is where
gpg-agent 2.0.24 usually puts its socket.
> FYI, I initially disabled GNOME Keyring by adding the following lines to a
> startup script:
> killall gpg-agent
> killall gnome-keyring-daemon
> gpg-agent --daemon --enable-ssh-support --write-env-file
> "${HOME}/.gpg-agent-info"
> . "${HOME}/.gpg-agent-info"
> export GPG_AGENT_INFO
> export SSH_AUTH_SOCK
> gnome-keyring-daemon --components=ssh,secrets,pkcs11
you say "a startup script", but it's not clear to me where this happens.
Most likely, setting environment variables in a script that you run at
startup probably *won't* export them to other portions of your user
session, because the script runs in a "sibling" process instead of
acting as the ancestor of the rest of your session.
With a normal X11 setup in debian, i'd have expected
/etc/X11/Xsession.d/90gpg-agent to start up the gpg-agent in the right
way for you already, as long as the gnome keyring daemon wasn't
squatting the environment variable already :/
I don't know enough about ubuntu's session-handling to know the right
way to advise you concretely on ubuntu, though.
--dkg
signature.asc
Description: OpenPGP digital 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
