I have had a problem with the seahorse application for a few days. Before, it started when I started my system, I unlocked and I was comfortable with my encrypted ssh keys, etc.
Now, for some reason that is unknown to me (ok, I changed my ssh key/passphrase without using seahorse ?!), it does not start at startup. Worse, I can’t normally connect in ssh with registered remote hosts. For example, to connect to a remote machine in ssh on which I saved the key, I get the answer “sign_and_send_pubkey: signing failed: agent refused operation”. For sweater on a github repository, same problem. (of course, I tried to change the keys, using directly seahorse… There is always the same message then)
I can of course do a trick to use the ssh agent, but then I have to enter my key each time.
I don’t know where to start to fix this problem. I would like to come back to the situation of unlocking at startup, and letting seahorse manage my ssh keys.
I tried lot of things found on the Internet… But I need some help. Please
It is working fine here. However, I did not change ssh passphrase, so I don’t know how that affects things.
Here’s one difference, though. For me, the Gnome login keyring is already open when I login to Gnome. It is using the login password for that. So maybe you are using auto-login, and never give your password.
So I wonder whether you ever changed your login password, and whether that would affect anything.
Can you post the output of
zypper lr -d
We might as well look at your repos. It’s always possible that a rogue repo is causing problems.
I fixed the problem. After reinstall OpenSuse, I kept my ssh and configuration from the previous install, and I had exactly the same problem.
I only removed all the .ssh/* content, recreated a ssh key using seahorse, and it seams to work, now.
I don’t know what was the problem… But now it’s solved.