Re: SSH_AUTH_SOCK behavior is completely insane

On 11/23/2017 03:20 AM, cen wrote: According to other replies gnome-keyring is involved so perhaps the fault lies in that. I doubt upstream ssh guys would override cli options with agent. Nonsense.  GNOME provides *an* agent, it doesn't modify ssh.  The ssh client decides what order to at

Re: SSH_AUTH_SOCK behavior is completely insane

According to other replies gnome-keyring is involved so perhaps the fault lies in that. I doubt upstream ssh guys would override cli options with agent. Cli is usually the highest order of priority. I will try to investigate further and try to pinpoint the blame. For now I managed to completel

Re: SSH_AUTH_SOCK behavior is completely insane

Not sure why but setting IdentityAgent in config did nothing for me. Perhaps this is a problem with gnome-keyring being overzealous and always trying to be first. On 11/23/2017 04:15 AM, Christopher wrote: On Wed, Nov 22, 2017 at 6:07 PM cen > wrote: Whose good

Re: SSH_AUTH_SOCK behavior is completely insane

I tried IdentitiesOnly and it worked but it also disables password login which I sometimes need. On 11/23/2017 02:29 AM, Todd Zullinger wrote: cen wrote: Anyone doing linux admin or dev work has more than 5 keys in their .ssh directory, rendering the agent completely USELESS PIECE OF SHIT PR

Re: SSH_AUTH_SOCK behavior is completely insane

I did use -v and it does use other keys first. It probably uses my key down the road but you can never see that because remote blocks you before it happens. On 11/23/2017 01:53 AM, Cameron Simpson wrote: On 23Nov2017 00:06, cen wrote: Whose good idea in the history of Linux was to turn ssh a

Re: SSH_AUTH_SOCK behavior is completely insane

This is not just Fedora specific behavior. I ran into this a few days ago on a Mac after adding a bunch of keys to my agent (one per AWS region). Even if you specify a key with “-i” it will still go for the agent, resulting in an Auth failure. Not sure if specifying a key in the config will over

Re: SSH_AUTH_SOCK behavior is completely insane

On Wed, Nov 22, 2017 at 6:07 PM cen wrote: > 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

Re: SSH_AUTH_SOCK behavior is completely insane

Tom Horsley wrote: On Thu, 23 Nov 2017 00:06:11 +0100 cen wrote: 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. Why? I do lots of linux admin work and I only have two keys. I use a different

Re: SSH_AUTH_SOCK behavior is completely insane

cen wrote: 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. Not at all. It just requires some config to handle that well. :) Does everyone disable agent first thing after installing Fedora? How e

Re: SSH_AUTH_SOCK behavior is completely insane

On 23Nov2017 00:06, cen wrote: 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 Authentica

Re: SSH_AUTH_SOCK behavior is completely insane

On Thu, 23 Nov 2017 00:06:11 +0100 cen wrote: > 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. Why? I do lots of linux admin work and I only have two keys.

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 S