Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fingerprint on SFTP differs from SSH #8175

Closed
cyberduck opened this issue Aug 14, 2014 · 5 comments
Closed

Fingerprint on SFTP differs from SSH #8175

cyberduck opened this issue Aug 14, 2014 · 5 comments
Assignees
Labels
bug fixed sftp SFTP Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

ae537c6 created the issue

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #8173. Fix in 2f9ed9c.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

ae537c6 commented

Thanks dkocher for your fast reply. The new snapshot indeed gives me the correct fingerprint.

Also, apologies for the duplicate, there was some time between searching the tickets and filing one myself...

Also, can Cyberduck automatically use the key in .ssh for logging in with a key? (Transmit does this, it's quite nice)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 matthijs zwinderman]:

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 setting ssh.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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 dkocher]:

Replying to [comment:3 matthijs zwinderman]:

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 setting ssh.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.

Documentation updated in Default Public Key Authentication Keys.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed sftp SFTP Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants