gpg-agent, ssh-agent, and keychain confusion

[Norman Walsh]

Are gpg-agent, ssh-agent, and keychain really supposed to get along?

If you start gpg-agent, it exports SSH_AUTH_SOCK

If you start ssh-agent, it exports SSH_AUTH_SOCK

No matter which you start first, the second provides a different
socket, so it would appear that they don't get along.

After gpg-agent is installed, the X11 boot process no longer starts
ssh-agent (because the SSH_AUTH_SOCK is already defined).

But if you run keychain, it does attempt to start ssh-agent at which
point either ssh-add or gpg is confused.

It appears that starting gpg-agent is sufficient; gpg-agent handles
both ssh connections and gnupg keys.

But in that case keychain seems broken.

Somewhere, there's some incompatibility here.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw at nwalsh.com> | Human history becomes more and more a
http://nwalsh.com/            | race between education and
                              | catastrophe.--H. G. Wells
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060601/805e03e4/attachment.sig>