SSH_AUTH_SOCK behavior is completely insane
Whose good idea in the history of Linux was to turn ssh agent on by
default when one has more than 5 private keys available? This is what I
just got:
ssh -i mykey.pem user@myhost
Received disconnect from ... port 22:2: Too many authentication failures
Authentication failed.
Then I do export SSH_AUTH_SOCK="" and surprise! I am logged in. And I am
not even sure why this suddenly stopped working, I swear to God
specifying the key used to override the agent.
So apparently the agent even overrides my -i flag which explicitly
specifies which key to use. Instead of taking my key as I specify, ssh
agent will go and try every single key file in my .ssh directory and
fail after 5 times because any sane remote ssh server will block you
after failing so many times.
Anyone doing linux admin or dev work has more than 5 keys in their .ssh
directory, rendering the agent completely USELESS PIECE OF SHIT PROGRAM.
Does everyone disable agent first thing after installing Fedora? How
else do you even manage to survive with this crap running?
Why would agent even try with other keys if I SPECIFY the goddamn key!
It doesn't make any sense!
How do I turn it off in all shells for all users forever? How do I nuke
this from system? .bash_profile export does not seem to cut it.
Not to mention the same shit happens when you open gnome files and try
to connect to remote location, except you can't even specify the key in
the UI. It will just try a bunch of keys until you are blocked by remote.
And there are numerous other programs who do this, like Filezilla.
I just don't get it apparently..