ssh public key auth fails after hibernate

[Alexander Savchenko]

Hardy (updated from Gutsy). Public key auth works fine after boot but fails after hibernate. Here is the log:

...
debug2: key: /home/dizel/.ssh/identity ((nil))
debug2: key: /home/dizel/.ssh/id_rsa (0xb7fa8610)
debug2: key: /home/dizel/.ssh/id_dsa (0xb7fa8628)
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/dizel/.ssh/identity
debug1: Offering public key: /home/dizel/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Offering public key: /home/dizel/.ssh/id_dsa
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: Next authentication method: password

[Wayne Scott (wsc9tt)]

I see similar problems after restarting from a hibernate attempts to ssh or call ssh-add freeze.
I find that SSH_AUTH_SOCK still set in the environment and pointing a gnome-key process that is
still running.

[Craig73 (funrun73)]

Alex, have you tried this in Intrepid (8.10)? Do you have problems with this there?

[Caspar Clemens Mierau (leitmedium)]

Marking as incomplete as we are waiting for an answer.

[Wayne Scott (wsc9tt)]

Sorry, no longer have that laptop so I can't reproduce the bug anymore.

2009/2/21 Caspar Clemens Mierau <email address hidden>

> Marking as incomplete as we are waiting for an answer.
>
> ** Changed in: openssh (Ubuntu)
> Status: New => Incomplete
>
> --
> ssh public key auth fails after hibernate
> https://bugs.launchpad.net/bugs/228656
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Chuck Short (zulcss)]

Closing then, user is no longer able to reproduce.

Regards
chuck