4

before plasma 5 I had my kwallet unlocked at login and it worked well (same password for kwallet as for my session).

Now, with plasma 5, it does not work anymore, I think I'm not far from working this out, but I don't know what to do next.

Here is my setup, in ~/.config/plasma-workspace/env/ssh-agent.sh :

#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)
/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite

Note that I load 2 keys whith ssh-add. After login in, I have to unlock my wallet 2 times before the desktop shows up.

Anybody see What is going wrong ?

Thanks a lot.

skizo
  • 731
  • 4
  • 5

1 Answers1

0

I have a workaround that I don't want to use anymore maybe it helps someone.

Add the following if statement around your ssh-add command:

#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)

if pstree -s -p $$ | grep Xsession; then
    exit
fi

/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite

Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.

iRaS
  • 296