Bug 498112 - ssh-add -c doesn't require confirmation
Summary: ssh-add -c doesn't require confirmation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 19
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-28 21:54 UTC by Jonathan Smith
Modified: 2016-04-23 17:45 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:14:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Smith 2009-04-28 21:54:33 UTC
Description of problem:
ssh-add -c should, according to the man page, require confirmation before using the cached key. This works in RHEL5, but not in rawhide. Unfortunately, I am not in a position where I'm able to test anything in between RHEL5 and current rawhide.

When you attempt to use -c, you get a warning, shown below.

user@boxname ~ $  ssh-add -c
Enter passphrase for /home/user/.ssh/id_rsa: 
SSH_AGENT_FAILURE
Identity added: /home/user/.ssh/id_rsa (/home/user/.ssh/id_rsa)

Then when using the ssh key by, for instance, sshing to a machine, no confirmation is shown, and the key is used anyway.

Version-Release number of selected component (if applicable):
openssh-5.2p1-2.fc11.x86_64
openssh-askpass-5.2p1-2.fc11.x86_64
openssh-clients-5.2p1-2.fc11.x86_64

Comment 1 Tomas Mraz 2009-04-29 06:43:57 UTC
Note that the rawhide does not use the ssh-agent from the openssh package by default but it uses gnome-keyring daemon instead of it.

Comment 2 Bug Zapper 2009-06-09 14:43:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Matthias Clasen 2009-06-11 17:01:46 UTC
Reported upstream in http://bugzilla.gnome.org/show_bug.cgi?id=525574

Comment 4 Bug Zapper 2010-04-27 13:59:01 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Jonathan Smith 2010-04-28 00:00:17 UTC
This is still a problem in 13...

Comment 6 Paul DeStefano 2011-03-09 01:52:40 UTC
Oh, I was so hoping this bug would explain everything.  I would really like to know what is the status with this whole issue.

I've been waiting for gnome-keyring-daemon to start honoring these constraints is some way (from ssh-add).  It seems like this would just fix everything.  Isn't this going to be implemented?

Or, seahrose needs to allow these constraints to be placed on keys (individually).  That would work too, but that amounts the the same thing, right?

And/Or, some reliable way to remove gnome-keyring-daemon needs to be documented.  I've tried to disable the ssh support in gnome several different ways and none of them work; it's still the agent for all my ssh stuff.  I don't think it's reasonable to have to uninstall core packages or fiddle with pam just to get the correct behavior (which was working fine before gnome-keyring took over ssh-agent duties).

Regardless, it would be greatly appreciated if someone would just explain what's going on and what is the long-term plan to address this issue.

Also, this is an on-going issue, and this bug affects Fedora 14.  At the very least, that should be updated in this bug so it doesn't get closed.

Comment 7 Fedora End Of Life 2013-04-03 19:05:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 8 Fedora Admin XMLRPC Client 2013-05-08 22:41:44 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Till Maas 2014-10-08 18:36:19 UTC
This is IMHO a security issue and should get a CVE.

Comment 10 Fedora End Of Life 2015-01-09 16:12:35 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2015-02-17 13:14:18 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 12 Florian Weimer 2016-04-23 17:45:15 UTC
gnome-keyring recognizes this now:

$ ssh-add
Could not add identity "/home/fweimer/.ssh/id_rsa": communication with agent failed

Apr 23 19:43:46 oldenburg.str.redhat.com gnome-keyring-daemon[4360]: prompt constraints are not supported.


Note You need to log in before you can comment on or make changes to this bug.