Bug 18789
| Summary: | ssh ``dumb'' about DSA keys held by ssh-agent | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <oneill> |
| Component: | openssh | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | dr, paskalis, pekkas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-02-02 16:34:28 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: | |||
This is not quite true in my experience-- Openssh to ssh2 server version 2.3.0 works fine with the agent and no prompting. Openssh to ssh2 server version 2.1.0 doesn't work with the information it gets from the agent, but it is able to get the same key from the same id file after it prompts for the passphrase. -- ddj Check the permissions of the remote ~/.ssh/authorized_keys2 file. The manpage suggests some. Sarantis Do you see this behaviour with more recent versions of OpenSSH? Have you checked the permissions? If there are still problems, please provide more data by running ssh -v -v -v and sshd -d -d -d. No response from reporter. |
When ssh connects to a machine that doesn't recognize any of the DSA keys held by ssh-agent, ssh will try ~/.ssh/id_dsa even if ssh-agent has already provided an unlocked copy of ~/.ssh/id_dsa. This means that the user is pointlessly prompted for a passphrase for a DSA key that won't be accepted. M.E.O.