Too many authentication failures with many keys available in ssh-agent

[cyberduck]

f21dfa2 created the issue

Dear Cyberduck team,
with v7.8.3 I get "too many authentication failures" for a login. v7.7.2 works fine, as does the ssh login via terminal.
The login is configured in the ssh config file and uses a ssh key based login via ssh-agent.
In the ssh config I have to set 'IdentitiesOnly yes', otherwise the server usually rejects a login as there are many keys in my ssh agent.
Is it possible Cyberduck tries all the keys from the ssh-agent which then leads to the "too many authentication failures" at some point?

many TIA

[cyberduck]

@dkocher commented

I can confirm this is probably the cause as we try agent based authentication first.

[cyberduck]

@dkocher commented

IdentitiesOnly
Specifies that ssh(1) should only use the authentication identity files configured in the ssh_config files, even if ssh-agent(1) offers more identities. The argument to this keyword must be yes or no. This option is intended for situations where ssh-agent offers many different identities. The default is no.

[cyberduck]

@dkocher commented

Relates to #9964.

[cyberduck]

@dkocher commented

We will see if we can add support for the IdentitiesOnly directive from the OpenSSH configuration.

[cyberduck]

@dkocher commented

Could you please share your OpenSSH configuration for reference.

[cyberduck]

@dkocher commented

In 6120054.

[dkocher]

Follow up in #13947 with the option read IdentityFile configuration directive to limit authentication attempts using agent.