Hi, Yes, you are true. There are ways to work around this by changing the network configuration. The problem with nautilus is that it seems not to identify an SSH connection by an address/port tuple. Even if the host identification has changed, it should not connect to a completely different port.
Please note that the command line client still gives you a choice to log in with a private key. Using one, I simply get the following notification: " Password authentication is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Enter passphrase for key 'XXXXXX': " So I think using a private key, I should simply receive a notification from nautilus and then be able to connect. -- Access to remote SSH server does not distinguish the connection by port https://launchpad.net/bugs/59882 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
