Client fails to connect: too many identiies: IdentitiesOnly not available?
Posted: 2019-07-16 21:01
Is there a setting that tells the client to use (or ignore) identities?
There appears to be no way to configure the filezilla client and it simply does not honor the ~/.ssh/config (see below)
For some SSH servers (like the default ones in AWS), the daemon is built to allow only a certain number of attempts before rejecting the request (whether by key or password).
(In AWS its 6 the default for Open SSH). If you have more than the number of keys in the ~/.ssh directory, the login to such servers will always fail.
On the SSH command line, giving the IdentityOnly=yes setting(https://superuser.com/questions/268776/how-do-i-configure-ssh-so-it-dosent-try-all-the-identity-files-automatically) tries only the specific identity file given.
Alternatively, in the SSH configuration (~/.ssh/config) the follow also works:
Host *
IdentitiesOnly yes
In https://remmina.org/ using password authentication and a no identity file also works (if a key is used: the ~/.ssh/config setting is honored).
There appears to be no way to configure the filezilla client and filezilla simply does not honor the ~/.ssh/config settings
There appears to be no way to configure the filezilla client and it simply does not honor the ~/.ssh/config (see below)
For some SSH servers (like the default ones in AWS), the daemon is built to allow only a certain number of attempts before rejecting the request (whether by key or password).
(In AWS its 6 the default for Open SSH). If you have more than the number of keys in the ~/.ssh directory, the login to such servers will always fail.
On the SSH command line, giving the IdentityOnly=yes setting(https://superuser.com/questions/268776/how-do-i-configure-ssh-so-it-dosent-try-all-the-identity-files-automatically) tries only the specific identity file given.
Alternatively, in the SSH configuration (~/.ssh/config) the follow also works:
Host *
IdentitiesOnly yes
In https://remmina.org/ using password authentication and a no identity file also works (if a key is used: the ~/.ssh/config setting is honored).
There appears to be no way to configure the filezilla client and filezilla simply does not honor the ~/.ssh/config settings