This is a security bug as it is now, as if one uses agent forwarding, it
is impossible to confirm the use of a certain key on a (possible
compromized) machine. Still present in 15.04 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, the linked debian bug is incorrect, as it is about using different
key format; and this bug is about having the keyring interactively
confirm each key signing request over the agent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: gnome-keyring (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading response length from authentication socket.
** Bug watch added: Debian Bug tracker #738660
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660
** Also affects: gnome-keyring (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660
Importance: Unknown
Status: Unknown
--
You received this bug notification
The same symptoms seem to still be present in 14.04.1 LTS at least for
ed25519 keys. RSA keys seem to work ok.
$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
$ apt-cache policy gnome-keyring
gnome-keyring:
Installed: 3.10.1-1ubuntu4.1
Candidate: 3.10.1-1ubuntu4.1
** Bug watch added: GNOME Bug Tracker #525574
https://bugzilla.gnome.org/show_bug.cgi?id=525574
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=525574
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Looks like a duplicate of 209447.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading response length from authentication socket.
To manage notifications about this
That's bug 209447.
*glares at Launchpad*
*grumbles about lack of a Preview button*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading response length from
** Changed in: gnome-keyring
Status: Unknown = Confirmed
** Changed in: gnome-keyring
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Are you sure that you're connected to ssh-agent and not to some other
agent like gnome-keyring-daemon? Please can you run:
eval `ssh-agent`
and then try again with ssh-add -c in the same shell to verify?
--
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
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/1067301
Title:
ssh-add: Error reading response length from
It then gives the error Agent admitted failure to sign using the key.
$ eval `ssh-agent`
Agent pid 9903
$ ssh-add -c /home/user/.ssh/key_rsa
Enter passphrase for /home/user/.ssh/key_5501_rsa:
Identity added: /home/user/.ssh/key_rsa (/home/user/.ssh/key_rsa)
The user must confirm each use of
You also need to set SSH_ASKPASS and DISPLAY appropriately. Please see
the ssh-add and ssh-agent manpages.
I've just checked behaviour on Quantal and as far as I can see,
everything is working as expected, so I believe this to be a local
configuration issue and not a bug. So I'm marking this bug
An afterthought: I think I've been thinking of this too much from the
perspective of openssh. I suppose it would be a valid wishlist bug that
gnome-keyring doesn't support the confirmation mechanism by default. But
that would be a bug in gnome-keyring rather than in openssh. But please
go ahead
This is with a plain vanilla Quantal (Lubuntu) installation installed
just today and have not changed the configurations on. So the settings
used are default. SSH_ASKPASS is not getting set:
$ echo $SSH_ASKPASS
$ echo $DISPLAY
:0
--
You received this bug notification because you are a member
** Package changed: openssh (Ubuntu) = gnome-keyring (Ubuntu)
** Changed in: gnome-keyring (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Are you sure that you're connected to ssh-agent and not to some other
agent like gnome-keyring-daemon? Please can you run:
eval `ssh-agent`
and then try again with ssh-add -c in the same shell to verify?
--
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading response length from authentication socket.
To
It then gives the error Agent admitted failure to sign using the key.
$ eval `ssh-agent`
Agent pid 9903
$ ssh-add -c /home/user/.ssh/key_rsa
Enter passphrase for /home/user/.ssh/key_5501_rsa:
Identity added: /home/user/.ssh/key_rsa (/home/user/.ssh/key_rsa)
The user must confirm each use of
You also need to set SSH_ASKPASS and DISPLAY appropriately. Please see
the ssh-add and ssh-agent manpages.
I've just checked behaviour on Quantal and as far as I can see,
everything is working as expected, so I believe this to be a local
configuration issue and not a bug. So I'm marking this bug
An afterthought: I think I've been thinking of this too much from the
perspective of openssh. I suppose it would be a valid wishlist bug that
gnome-keyring doesn't support the confirmation mechanism by default. But
that would be a bug in gnome-keyring rather than in openssh. But please
go ahead
This is with a plain vanilla Quantal (Lubuntu) installation installed
just today and have not changed the configurations on. So the settings
used are default. SSH_ASKPASS is not getting set:
$ echo $SSH_ASKPASS
$ echo $DISPLAY
:0
--
You received this bug notification because you are a member
** Package changed: openssh (Ubuntu) = gnome-keyring (Ubuntu)
** Changed in: gnome-keyring (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
24 matches
Mail list logo
