I've had the same issue as the original reporter since my clean install of jaunty, but brynhood's comment above about public keys inspired me to check to see if I even had a public key in my .ssh directory. I did not. Creating one (id_rsa.pub) from my private key (id_rsa) apparently solved part of the problem -- instead of being asked for my passphrase at the console, a gnome dialog popped up instead. However, successful entry of my passphrase still did not result in a successful login, even though my private key was unlocked and cached in the seahorse agent. Here's the debug info from an unsuccessful ssh attempt (which works fine if id_rsa.pub does *not* exist, and as such I enter my passphrase at the console):
[...] debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/brian/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 276 [at this point, the gnome dialog popped up and asked for my passphrase] debug1: Authentications that can continue: publickey debug1: Trying private key: /home/brian/.ssh/identity debug1: Trying private key: /home/brian/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). -- ssh-add/ssh-askpass (gnome) not launching graphical prompt on connect. ubuntu 9.04 https://bugs.launchpad.net/bugs/375341 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
