Could this be related to 302252, which I reported last week.
Similarities include: 1) ssh uses the wrong "-i id_rsa-..." key, 2) noticed
shortly after upgrade.
I'm using id_rsa, instead of id_dsa. Unlike this bug, the workaround
(removing the default key) does not work.
--
ssh client not using
The problem goes away if I manually kill the gnome-keyring-daemon
If not killed, /var/log/auth.log contains suspicious entries such as...
Dec 5 17:12:30 slzlr7 gnome-keyring-daemon[5489]: Unsupported or unknown SSH
key algorithm: command="echo
Dec 5 17:12:30 slzlr7 gnome-keyring-daemon[5489]:
See also my comments on bug 271184
--
openssh sshd authorized_keys wrong command= (statefull value?)
https://bugs.launchpad.net/bugs/302252
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.ub
see also gnome keyring bug 275010
--
openssh sshd authorized_keys wrong command= (statefull value?)
https://bugs.launchpad.net/bugs/302252
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.ubu
gnome-keyring bugs may be the root cause of the openssh bug 302252 that
I reported last week.
I clobbered several Subversion source code repositories that I access
via svn+ssh.
I can manually kill gnome-keyring-daemon to work around.
Wish ssh-agent was still the default :^(
--
Unable to disabl
