*** This bug is a duplicate of bug 201786 ***
https://bugs.launchpad.net/bugs/201786
** This bug has been marked a duplicate of bug 201786
ssh Agent admitted failure to sign using the key on big endian machines
--
You received this bug notification because you are a member of Ubuntu
Affected here too after creating a new key in ~/.ssh, this is 14.04 with
all updates as of today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires
Although the fix above works for ssh I cannot connect with filezilla and
get the following error:
Pageant failed to answer challenge
So I removed SSL_AUTH_SOCK from .bashrc and could then connect again
with filezilla, but not ssh.
After a look around I can connect with ssh using the following
I forgot to mention:
uname -a
Linux robs-tosh-L50-a 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
ssh -V
OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
--
You received this bug notification because you are a member of Ubuntu
Server
This bug has hit me quite hard in the last week, breaking a number of
automated ssh processes that have been working without a hitch prior to
sometime after Monday evening (8 December, UTC+8) this week. I can pin
it down to that because each Monday and Friday evening I use a scripted
ssh tunnel
Also (because it is a different result from one posted earlier):
echo ${SSH_AUTH_SOCK}
/run/user/1000/keyring-X8I7Ly/ssh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
The workaround to put export SSH_AUTH_SOCK=0 in my .bashrc also for me
on 14.04 with the following versions:
$ ssh -V
OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
$ uname -a
Linux mycomputer 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC
2014 x86_64 x86_64
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.
Fix works for me too, but it obviously isn't the proper solution.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires SSH_AUTH_SOCK=0 will not work
Hi,
I confirm this problem with 2 other computers. It seems to be link to Unity or
Gnome keyring and ssh-agent.
It does not happen with a KDE desktop. If you press ctrl+alt+F1 and test your
ssh connexion, it should work due to environment variables where echo
$SSL_AUTH_SOCK return an empty
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
What is the value of $SSH_AUTH_SOCK before you attempt to override it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires SSH_AUTH_SOCK=0 will not
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
** 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
16 matches
Mail list logo
