Bug 18789 - ssh ``dumb'' about DSA keys held by ssh-agent
ssh ``dumb'' about DSA keys held by ssh-agent
Product: Red Hat Linux
Classification: Retired
Component: openssh (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Depends On:
  Show dependency treegraph
Reported: 2000-10-10 05:19 EDT by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-02 11:34:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-10-10 05:19:25 EDT
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.

Comment 1 David D. Johnson 2000-11-02 08:30:12 EST
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
Comment 2 Sarantis Paskalis 2000-12-22 06:53:20 EST
Check the permissions of the remote ~/.ssh/authorized_keys2 file.
The manpage suggests some.

Comment 3 Pekka Savola 2001-01-12 15:05:12 EST
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.
Comment 4 Tomas Mraz 2005-02-02 11:34:28 EST
No response from reporter.

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