gnome-keyring asks for passphrase for plain `ssh-add -l'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-keyring (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
I've a script I run on first logging in. I've used it for years, since
Ubuntu 5.04 and earlier. One of the things it does is an ssh-add so my
passphrase can be entered, but I don't want to run that if an ssh-add
has already been done so I used to do `ssh-add -l' and check the output
for a line where the third word was `/home/
Recently, with 8.04 I think, that's no longer a valid test. The output
when I've already entered the passphrase has changed to
$ ssh-add -l
1024 9d:5a:9a:
1024 9d:5a:9a:
$
So instead I thought I'd change to checking if $2 was
`9d:5a:
in for the first-time, immediately after booting, if I do an `ssh-add
-l' a dialogue pops up asking for a passphrase. I cancel that by
pressing Escape. Why would merely attempting to *list* the fingerprints
of all the agent's keys ask for a passphrase?
A side effect of that diaglogue popping up is that ssh-add will now line
one key, but not two. I still haven't entered any passphrase at this
point.
$ ssh-add -l
1024 9d:5a:9a:
$
If I then do `ssh-add' and enter the passphrase then I get two lines of
output.
$ ssh-add -l
1024 9d:5a:9a:
1024 9d:5a:9a:
$
So, what's the significance of one or two lines of output given they're
identical, and why does listing the agent's keys' fingerprints ask for a
passphrase when it never used to?
The above was originally https:/ /answers. launchpad. net/ubuntu/ +source/ openssh/ +question/ 36438 rather than a bug. However, on thinking about it, prompting for the passphrase for `ssh-add -l' seems broken compared to the old behaviour.