Is there an existing request for this?
Is your feature request related to a problem?
"sftp: Failure establishing SSH session (-5)"
Please correct me if I'm wrong, but, currently, it seems this error message is given in multiple cases: (1) that a host does not exist in the "known_hosts" file; (2) that a host exists but has a new/non-matching key; (3) that the host does not support compatible KexAlgorithms/HostKeyAlgorithms.
It would be great if the error message given would specifically describe which case, as right now it gives no clues of how to rectify it.
The last case can be most confusing/frustrating (at least to a new/novice user such as myself), since MidnightCommander uses OpenSSH's "known_hosts" file but not its KexAlgorithms/HostKeyAlgorithms. This means that "ssh" and "sftp" CLI commands will often work while MidnightCommander will fail--giving only that indescriptive error message.
Describe the solution you'd like
More descriptive error messages
Describe alternatives you've considered
No response
Additional context
No response
Is there an existing request for this?
Is your feature request related to a problem?
"sftp: Failure establishing SSH session (-5)"
Please correct me if I'm wrong, but, currently, it seems this error message is given in multiple cases: (1) that a host does not exist in the "known_hosts" file; (2) that a host exists but has a new/non-matching key; (3) that the host does not support compatible KexAlgorithms/HostKeyAlgorithms.
It would be great if the error message given would specifically describe which case, as right now it gives no clues of how to rectify it.
The last case can be most confusing/frustrating (at least to a new/novice user such as myself), since MidnightCommander uses OpenSSH's "known_hosts" file but not its KexAlgorithms/HostKeyAlgorithms. This means that "ssh" and "sftp" CLI commands will often work while MidnightCommander will fail--giving only that indescriptive error message.
Describe the solution you'd like
More descriptive error messages
Describe alternatives you've considered
No response
Additional context
No response