You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting to my server over a local connection I get a different fingerprint using Cyberduck than from the regular "SSH" or "SFTP" or "SCP" command in Terminal.
The fingerprint I get from Cyberduck ends in :63, while the fingerprint from SSH ends in :66
These two should not differ.
Things I've tried:
I listed the fingerprints of all the keys on my server (with "ssh-keygen -lf"), even the ones that are not in use (DSA). None match Cyberduck's fingerprint.
I've used Wireshark to check that Cyberduck connects directly with the right server (both SSH and Cyberduck follow the same path)
Ive tried connecting through a router, still get the wrong fingerprint
The only thing I can imagine is Cyberduck calculating the fingerprint in a different way than SSH.
The text was updated successfully, but these errors were encountered:
Also, can Cyberduck automatically use the key in .ssh for logging in with a key? (Transmit does this, it's quite nice)
You can set the hidden settingssh.authentication.publickey.default.enable to true to enable the use of ~/.ssh/id_rsa or ~/.ssh/id_dsa (in that order) if the keys exist.
Also, can Cyberduck automatically use the key in .ssh for logging in with a key? (Transmit does this, it's quite nice)
You can set the hidden settingssh.authentication.publickey.default.enable to true to enable the use of ~/.ssh/id_rsa or ~/.ssh/id_dsa (in that order) if the keys exist.
When connecting to my server over a local connection I get a different fingerprint using Cyberduck than from the regular "SSH" or "SFTP" or "SCP" command in Terminal.
The fingerprint I get from Cyberduck ends in :63, while the fingerprint from SSH ends in :66
These two should not differ.
Things I've tried:
The only thing I can imagine is Cyberduck calculating the fingerprint in a different way than SSH.
The text was updated successfully, but these errors were encountered: