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

Include port number when saving host key fingerprint #11255

Closed
cyberduck opened this issue Nov 20, 2020 · 2 comments
Closed

Include port number when saving host key fingerprint #11255

cyberduck opened this issue Nov 20, 2020 · 2 comments
Labels
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 20, 2020

@dkocher created the issue

But because you do not store the port number it will cause issues. Perhaps
I did not explain this properly.

For example, if you setup SSH port forwarding tunnels:

127.0.0.1:5000 > 10.0.1.50:22
127.0.0.1:5001 > 10.0.1.51:22
127.0.0.1:5028 > 10.0.7.32:22
127.0.0.1:5176 > 80.xxx.xxx.xxx:22

These are port forwarding to unique servers with unique fingerprints.

In mountain duck if I connect to server1 and save the fingerprint, then
connect to server2, it will say the fingerprint has changed. If I save
server2 fingerprint and then connect to server1, it will say the key has
changed because it only stores the fingerprint for the IP, not IP:PORT.

OpenSSH has supported this for over 10 years.

This does not affect macOS.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 27, 2020

@ylangisc commented

In 73137a7.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 30, 2020

@dkocher commented

Milestone renamed

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

No branches or pull requests

1 participant