Bug 489336

Summary:	SSH connection with key not working in Wayland session
Product:	[I don't know] kde	Reporter:	Alex <acerlmt>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	mss
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alex 2024-06-27 19:15:38 UTC

SUMMARY
SSH connection not working, says `Too many authentication failures` in Wayland session. X11 work like a charm

STEPS TO REPRODUCE
1. Login to Wayland session
2. Open Konsole
3. Try login to server w/ ssh and key file, f.e. `ssh -i /path/to/key.pem root@<ip> -p 22`

OBSERVED RESULT
`Received disonnect from <ip> port 22:2: Too many authentication failures`

EXPECTED RESULT
`Enter passphrase for key '/path/to/key.pem':` - in X11 session

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.7.12-x64v4-xanmod1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
This bug was on Plasma 5 too

Comment 1 Malte S. Stretz 2024-06-30 16:36:41 UTC

I am not 100% sure but I guess you expect the ksshaskpass prompt to pop up? Then the issue is in upstream OpenSSH (and will be fixed in some future version, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068044) which doesn't recognize Wayland sessions as graphical sessions and thus never starts the askpass process.

You can try
env SSH_ASKPASS_REQUIRE=force ssh -i /path/to/key.pem root@<ip> -p 22
to see if that solves your issue.

If that doesn't solve it it is probably some other local configuration issue and you should ask on https://discuss.kde.org/tag/neon or https://webchat.kde.org/#/room/#kde-neon-users:kde.org for help.

Comment 2 Alex 2024-07-01 04:24:08 UTC

(In reply to Malte S. Stretz from comment #1)
> I am not 100% sure but I guess you expect the ksshaskpass prompt to pop up?
Yep

> env SSH_ASKPASS_REQUIRE=force ssh -i /path/to/key.pem root@<ip> -p 22
not solves issue

> If that doesn't solve it it is probably some other local configuration issue and you should ask on https://discuss.kde.org/tag/neon or https://webchat.kde.org/#/room/#kde-neon-users:kde.org for help.
OK, but it strange that bug in KDE Wayland session not interesting for `bugs.kde.org`🤷🏻‍♂️