Control: severity -1 important On zondag 17 juli 2016 19:02:09 CEST Diederik de Haas wrote: > Starting it from Konsole gave a somewhat unsettling result as it dumped > the password in plaintext to stdout ...
Lowering the severity as it looks like I was using it incorrectly, but keeping it to important as dumping a password in plaintext still doesn't sound right. > One thing I noticed when inspecting the debs from 5.6.5 and 5.7.0 was > that the /usr/share/application/org.kde.ksshaskpass.desktop file was > present in 5.6.5 but not in 5.7.0. > I guess that that explains the disappearance from krunner. > > When I run 'ssh-add' from Konsole thing seem to work just fine. I think > it's getting the password from kwallet (as before) and when I ssh into > another machine I'm not asked (again) for the password of my key. According to the README you should use it sth like the following. Put the following in a script: #!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass # Add default key ssh-add And then add/link that script in System Settings -> Autostart to be started at session start. I had removed that from my system as it meant that I often got 2 'competing' password dialog boxes at session start and that was annoying. One was from KMail/Kontact and the other from ksshaskpass and starting ksshaskpass manually through krunner as described earlier I didn't have that problem. But it could (very well) be that it was due to kwallet from 'KDE4' and 'KDE5' were asking for my password. But now I have the latest KMail (5.2.2), so they'd both use kwallet from 'KDE5' and after having created the above script and linking it in Autostart, I only got 1 password dialog box and both KMail and (k)ssh(askpass) are happy. I'm now also getting that ksshaskpass wants to open kwallet to retrieve the password, while I was getting a separate dialog before, probably some fallback mechanism.
signature.asc
Description: This is a digitally signed message part.
