Bug 498675 - ssh fail with generic "could not connect to host" error if key in known_hosts is wrong
Summary: ssh fail with generic "could not connect to host" error if key in known_hosts...
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.12.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-14 23:38 UTC by lesto
Modified: 2025-02-22 09:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
example error when connecting to host (37.48 KB, image/png)
2025-01-19 00:01 UTC, lesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lesto 2025-01-14 23:38:37 UTC
SUMMARY
if you try to ssh (fish://) into a host with invalid/wrong know_host, the error looks like is a connectivity issue

STEPS TO REPRODUCE
1. save a host key in know_host
2. change such key
3. try to connect with fish://

OBSERVED RESULT
Generic connectivity error

EXPECTED RESULT
Invalid key error, explanation of security implication, maybe even a button to replace the key
Comment 1 Nate Graham 2025-01-15 03:21:46 UTC
Could you attach a screenshot of the error dialog?
Comment 2 lesto 2025-01-19 00:01:38 UTC
Created attachment 177517 [details]
example error when connecting to host

alarm shared is defined as fish://alarm@192.168.178.234
Comment 3 TraceyC 2025-02-06 21:35:55 UTC
Here's what I see when I try to replicate on Dolphin 24.12.2 or built from git-master

1. I chose a host key in ~/.ssh/known_hosts
2. changed some characters in the key
3. try to connect in Dolphin with fish://hostname

There are *two* errors
1. The first one lets you know there's a fingerprint mismatch (a valid security warning)
"The authenticity of host 'hostname (IP)' can't be established.
xxx key fingerprint is...
This key is not known by any other name"

2. The error you reported and is shown in the screenshot
This is expected since the connection did indeed fail.

What do you expect to see at this point?
Comment 4 Bug Janitor Service 2025-02-21 03:46:45 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 lesto 2025-02-22 09:39:26 UTC
1. I chose ANOTHER host key in ~/.ssh/known_hosts
2. changed the ip
3. try to connect in Dolphin with fish://ip

i get only ONE generic error as per screenshot