Hmmm. Yeh, I've played a little more with this, and this always
triggers the problem. So try this to reproduce the problem:
(0) have a passphrase protected RSA key pair stored in ~/.ssh/id_rsa and
~/.ssh/id_rsa.pub
(1) logout of Gnome
(2) Ctrl-Alt-1
(3) login to the terminal
(4) delete the ~/.s
Hi again. I've just tested again, logging into localhost, with and
without myself in authorised keys and I observed the correct behaviour.
Can you enable a server on your own box and try logging into that?
Few things to try:
Try touching the authorised keys file.
disable gnome-keyring as the ssh
This is with a fresh install of hardy. Hmm. I'm definitely being
prompted for the key password regardless of whether the server accepts
it. In fact the server doesn't accept any authorized keys because the
authorized_keys file doesn't exist there. I should say this is just
after logging in on t
If both pubkeyauthentication and passwordauthentication are enabled on
the remote server , the ssh client will attempt the more secure method
first. If you do not want this, disable pubkey authentication in your
ssh client config and then pubkey authentication will be tried only if
you enable it
This might be relevant:
I am using seahorse-agent with ssh-agent rather than gnome-keyring-
daemon.
--
[Hardy] annoying and useless prompts
https://bugs.launchpad.net/bugs/221878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
