gpg-agent and ssh-keys not working anymore
Joke de Buhr
joke at seiken.de
Mon Apr 19 09:20:06 CEST 2010
I didn't have a host with gnupg version 2.0.15 ready so I regenerated the key
on a host with gnupg version 2.0.12 transfered my gnupg configuration back and
everything is working now with gnupg version 2.0.14.
Thank for a hint how to solve the problem.
The new ubuntu lucid which will be released in a few days and has a gpg-agent
version of 2.0.14. Though gpg-agent is not the default ssh-agent this problem
might cause trouble more in the next few months.
On Monday, 19. April 2010 08:35:03 Werner Koch wrote:
> On Fri, 16 Apr 2010 14:37, joke at seiken.de said:
> > The passwords are enter correctly and the ssh public key was added to
> > authorized_keys. I tried generating new ssh keys but the problem is
> > always the
> You might be hampered a bug fixed in 2.0.15:
> * Fixes a regression in 2.0.14 which prevented unprotection of new
> or changed gpg-agent passphrases.
> It is possible to write a tool to fix such a bad passphrases. However
> there are only a very few reports and thus I believe it is easier to
> generate a new key instead.
More information about the Gnupg-users