Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #8173


Ignore:
Timestamp:
Aug 13, 2014 7:45:09 AM (5 years ago)
Author:
Codifier
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8173 – Description

    initial v1  
    3333  Aug 13 07:55:39 Mac [0x0-0x21021].ch.sudo.cyberduck[341]: net.schmizz.sshj.transport.TransportException: [HOST_KEY_NOT_VERIFIABLE] Could not verify `ecdsa-sha2-nistp256` host key with fingerprint `f0:2a:ce:00:bf:cc:fe:15:51:32:42:42:7d:f8:08:be` for `[ip-address]` on port [port][[BR]]Aug 13 07:55:39 Mac Cyberduck[341]: [reader] ERROR net.schmizz.sshj.transport.TransportImpl - Dying because - {}\n\nnet.schmizz.sshj.transport.TransportException: [HOST_KEY_NOT_VERIFIABLE] Could not verify `ecdsa-sha2-nistp256` host key with fingerprint `f0:2a:ce:00:bf:cc:fe:15:51:32:42:42:7d:f8:08:be` for `[ip-address]` on port [port]\n      at net.schmizz.sshj.transport.KeyExchanger.verifyHost(KeyExchanger.java:206)\n  at net.schmizz.sshj.transport.KeyExchanger.handle(KeyExchanger.java:353)\n      at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:458)\n    at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:107)\n        at net.schmizz.sshj.transport.Decoder.received(Decoder.java:175)\n      at net.schmizz.sshj.transport.Reader.run(Reader.java:61)
    3434
    35 So, with my limited understanding, it appears Cyberduck ''is'' receiving the correct fingerprint, but can't verify it and subsequently still issues an unknown host message (with the wrong fingerprint).
     35So, with my limited understanding, it appears Cyberduck ''is'' receiving the correct fingerprint, but can't verify it yet subsequently still issues an unknown host message (with the wrong fingerprint).
    3636
    3737Lastly, on accepting this (wrong) unknown host fingerprint, the host is not added to my ~/.ssh/known_hosts file either and Cyberduck therefore repeatedly issues the same unknown host message.
swiss made software