Ksshaskpass, disable all kwallet integration?

Help
1

when invoking ksshaskpass i get

kf.config.core: Created a KConfigGroup on an inaccessible config location "kwalletrc" "Wallet"
kf.config.core: Created a KConfigGroup on an inaccessible config location "kwalletrc" "Wallet"
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
kf.config.core: Created a KConfigGroup on an inaccessible config location "kwinrc" "org.kde.kdecoration2"

I do not use kwallet (nor a sshagent most of the time)

Is there any way to make sure those things are disabled? I don’t see any command option on --help.

2

just realized that ksshaskpass is NOT a ssh askpass (in the tradition of x11-ssh-askpass), but a ssh-add frontend (to use kwallet, for when you call ssh-add without a terminal)!

shocking.

3

What are you talking about? Yes, you use it as an askpass program.

No, if you don’t want to use KWallet just don’t use ksshaskpass. That’s pretty much the only defining feature of it, use a GTK askpass or x11-askpass.

Edit: ah you opened sshaskpass only mode, debug for PromptType. (!23) · Merge requests · Plasma / KSSHAskPass · GitLab it seems, awesome!

4

Edit: ah you opened sshaskpass only mode,

sent that yesterday after I also noted the contradiction you showed on your message…

you use it as an askpass program.

if you don’t want to use KWallet just don’t use ksshaskpass.

I was abusing it as a generic ssh-askpass for a while, because i never bothered to look at the actual description and it worked well enough… and only looked at the code because of a small bug on SSH_ASKPASS_PROMPT handling. The source there only handle strings from ssh-add, and strangely enough, git. if the devs like that change I will add the strings for ssh (not ssh-add) use cases later. Because it looks pretty ugly now:

image
image1439×470 126 KB

[KWallet] the only defining feature of it

for me it is already having the qt/kde deps and UX consistency. Don’t want to add a bunch of gtk deps nor use unmaintained x11 application.

5

I’m taking the suggestion to move away from ksshaskpass. If anyone care about the patch above let me know as I’m not planning to work on it any further.