Bug 555646
Summary: | OpenSSH ignores keys in ~/.ssh/config and offers keys from Seahorse instead | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Phillip Smith <fukawi2+fedora> |
Component: | openssh | Assignee: | Jan F. Chadima <jchadima> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | ajschult784, fabsh, fukawi2+fedora, jchadima, mgrepl, tmraz, tschweikle |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-04 00:23:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Phillip Smith
2010-01-15 04:29:35 UTC
I think I ran into this bug or something similar when trying to push to Gitorious. I only have one SSH key which used to work but suddenly git reported the following on a push: Agent admitted failure to sign using the key. Permission denied (publickey). Regenerating the key and doing a "ssh-add ~/.ssh/id_rsa" fixed the problem. I think this is related to the follwing gnome-keyring / ssh-agent bug described in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786 I think that's a different problem. I do not see the error "Agent admitted failure to sign using the key". Then again, it *could* be the same problem manifesting differently. I was assuming this since Seahorse is involved. I am by no means an expert in all things SSH. I will file a separate bug if that is wanted. *shrugs* I'm not sure either -- I'm just saying that I don't get that exact error message.... Someone more knowledgeable than both of us in this area can determine hopefully ;) *** Bug 641684 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 Are we sure this is fixed in F14? I haven't had any problems so far but I haven't done much uploading to Gitorious lately (which is where this error would mostly surface for me). Did you test to use IdentitiesOnly ssh command? Maybe in some Host.... section? How would I go about doing that? man ssh_config Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed. |