Comment 6 for bug 1764044

I am a bit confused by the bug report.

I think ssh-add is correctly adding the DSA key to the agent, and the fact that running ssh-add again requests the password again is normal and expected. Looks Trusty behaves the same:

ubuntu@paride-t:~$ eval $(ssh-agent -s)
Agent pid 2406
ubuntu@paride-t:~$ ssh-add
Enter passphrase for /home/ubuntu/.ssh/id_rsa:
Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)
ubuntu@paride-t:~$ ssh-add
Enter passphrase for /home/ubuntu/.ssh/id_rsa:
Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)

So in my view this part of the bug is Invalid. @Rolf maybe you didn't realize as normally when ssh pubkey authentication just works there's no point in re-running ssh-agent?

I don't think keychain comes into play in this, as it is just a handy tool to manage the environment variables pointing to the ssh-agent socket. The password prompts are from ssh-add.

Then there is the fact that DSA keys have been deprecated from authentication, which is the root of the issue in my opinion. This is in my opinion a Wontfix, as heightening the security baseline requires deprecating older standards.

I'm moving this back to Incomplete.