[Cyberduck-trac] [Cyberduck] #11561: Refuses to connect

[Cyberduck]

#11561: Refuses to connect
-----------------------+----------------------
 Reporter:  agnonikov  |         Owner:
     Type:  defect     |        Status:  new
 Priority:  normal     |     Milestone:
Component:  sftp       |       Version:  7.8.1
 Severity:  normal     |    Resolution:
 Keywords:             |  Architecture:  Intel
 Platform:  macOS 11   |
-----------------------+----------------------
Description changed by dkocher:

Old description:

> CyberDuck refuses to connect to SFTP host, says "Too Many authentication
> failures", although there wasn't even one.
> Can connect from the same workstation to the same host using command line
> SFTP. The only guess I have - host has changed it's keys, so there can be
> conflict with previously recorded RSA key hash, although I have cleaned
> up known_hosts on OS, and I can't find where CyberDuck stores it's own
> known keys (if it does)
>
> error   21:50:29.471707+0100    Cyberduck       Dying because - Too many
> authentication failures.
> Subsystem ch.sudo.cyberduck  Category reader
> net.schmizz.sshj.transport.TransportImpl
>
> net.schmizz.sshj.transport.TransportException: [CONNECTION_LOST] Too many
> authentication failures.
>         at
> net.schmizz.sshj.transport.TransportImpl.gotDisconnect(TransportImpl.java:565)
>         at
> net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:521)
>         at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:113)
>         at net.schmizz.sshj.transport.Decoder.received(Decoder.java:203)
>         at net.schmizz.sshj.transport.Reader.run(Reader.java:60)
> <<kex done>> woke to: net.schmizz.sshj.transport.TransportException:
> [CONNECTION_LOST] Too many authentication failures.

New description:

 CyberDuck refuses to connect to SFTP host, says "Too Many authentication
 failures", although there wasn't even one.
 Can connect from the same workstation to the same host using command line
 SFTP. The only guess I have - host has changed it's keys, so there can be
 conflict with previously recorded RSA key hash, although I have cleaned up
 known_hosts on OS, and I can't find where CyberDuck stores it's own known
 keys (if it does)


 {{{
 error   21:50:29.471707+0100    Cyberduck       Dying because - Too many
 authentication failures.
 Subsystem ch.sudo.cyberduck  Category reader
 net.schmizz.sshj.transport.TransportImpl

 net.schmizz.sshj.transport.TransportException: [CONNECTION_LOST] Too many
 authentication failures.
         at
 net.schmizz.sshj.transport.TransportImpl.gotDisconnect(TransportImpl.java:565)
         at
 net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:521)
         at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:113)
         at net.schmizz.sshj.transport.Decoder.received(Decoder.java:203)
         at net.schmizz.sshj.transport.Reader.run(Reader.java:60)
 <<kex done>> woke to: net.schmizz.sshj.transport.TransportException:
 [CONNECTION_LOST] Too many authentication failures.
 }}}

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/11561#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows