ssh-agent is messed up

Hi,

Thanks for wasting many hours of my time, time I should have spend
reviewing linux kernel patches, by breaking ssh-agent.

I have a number of debian/testing systems, and on some of them gcr took
over ssh-agent, and this sorta works because its just a shim around the
actual ssh-agent. Now, I don't use GNOME, I despise GNOME, so 'apt
remove gcr' cured this.

Other machines, and the machines I've removed gcr from, magically end up
using gpg-agent, even though .gnupg/gpg-agent.conf does *NOT* have
'enable-ssh-support'. This is a *BUG*, this must not be!

The reason seems to be some gpg-agent-ssh.socket nonsense in systemd
that forces this. It also seems to race with the gcr thing, that also
wants to claim SSH_AUTH_SOCK.

Furthermore, it appears someone hobbled ssh-agent.service by removing
the [Install] section, so I can't even use that.

Anyway, gpg-agent doesn't act like a normal ssh-agent, it wants to
import the keys I add with ssh-add and store them in the gpg key
storage. This is *NOT* what an agent should do, it should just keep the
thing in RAM. I don't want extra copies of keys around, encrypted or
not.

Unfucking all this, on multiple machines (at leaset 3) is a major pain
in the arse. *AND* unasked for. You wrecked a perfectly working system.
All pain, no gain.

At least put in some of this fuckery in Debconf or so, and let the user
pick which actual agent to use. My preference is libpam-ssh to start
ssh-agent from the local user session (not the remote ones, that will
cause pain).


Yours, very grumpy,

Peter