guycarre is right in that this is a gnome/unity problem most likely. I
can confirm Ubuntu server 14.04.1 does not have this problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Is this what you mean?
echo $SSH_AUTH_SOCK
/tmp/ssh-5eicyaie79zk/agent.2453
That's as far as I got because Google would not tell me how to find the
socket value that was currently in use. Please tell me the command to
find the current socket value. I am eager to debug.
--
You received this
Public bug reported:
I expect that when using key based authentication I do $ssh user@0.0.0.0 I
expect to be asked for the key password. Instead I get Agent admitted failure
to sign using the key.
Permission denied (publickey).
Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked
** Attachment added: ssh_config.local
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231875/+files/ssh_config.local
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
** Attachment added: sshd_config.remote
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231905/+files/sshd_config.remote
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Happens with all SSH commands such as scp and sftp. This also means
that I can't use the file explorer called files to connect to remote
file systems. sftp will not work in the files browser because there is
no way to tell files to use SSH_AUTH_SOCK=0
So I can not browse remote files in the
Public bug reported:
In Precise the Bind9 db.root file is outdated. We need to keep this
file updated especially as Precise gets older over time. As time passes
this file will become more and more out of date. It may be possible to
backport just the single file and that would make an SRU
