* fully patched Fedora 19 * openssh-clients-6.2p2-7.fc19.x86_64 * ~/.ssh/config IdentityFile ~/.ssh/id_ecdsa IdentityFile ~/.ssh/id_rsa * both keys have the same password i call "ssh-add" in KDE's autostart to unlock my keys connecting to a RHEL7-Beta shows in /var/log/secure that id_rsa is used while from machines connecting via unencrypted private key per cronjob you can see there ECDSA Dec 13 14:36:55 hosting sshd[14110]: Accepted publickey for root from *.*.*.* port 51522 ssh2: RSA 81:15:32:31:87:78:2f:ad:e8:ba:78:b5:34:3a:b3:fc according to the manpage it should unlock both kyes and IMHO respect the order in ~/.ssh/config since we need both key-types as long not all servers and clients support ECDSA > ssh-add adds private key identities to the authentication > agent, ssh-agent(1). When run without arguments, it adds > the files ~/.ssh/id_rsa, ~/.ssh/id_dsa, ~/.ssh/id_ecdsa and > ~/.ssh/identity. After loading a private key, ssh-add > will try to load corresponding certificate information from > the filename obtained by appending -cert.pub to the name > of the private key file. Alternative file names can be given > on the command line. If any file requires a passphrase, ssh-add > asks for the passphrase from the user. The passphrase is read > from the user's tty. ssh-add retries the last passphrase if > multiple identity files are given.
ssh-add doesn't read config file. ssh client gets a list of keys from ssh-agent in order how they were added to the agent. If you want to prefer one key then add this key first: $ ssh-add .ssh/id_ecdsa .ssh/id_rsa Enter passphrase for .ssh/id_ecdsa: Identity added: .ssh/id_ecdsa (.ssh/id_ecdsa) Identity added: .ssh/id_rsa (.ssh/id_rsa) $ ssh-add -L ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAM9ObyBQNDv5nBeVfTA8qTfaqAlHOSmHeTv5YmiHhhI5XTSnhc/mKItd1djQVCYUPYOSGuAzEJPRETamBH/kdE= .ssh/id_ecdsa ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCqmBxx8ghdl8mTB2fbfvoJLK16MOtf0SeE70D6zcp0mLxu9J2u4mUU91ME+VZIgxX2oE04oLRg+e8nJVgfoPjOiZx5bvm0IMdqiPPE8qu9eiqqLVU5M385/ckHRzr1qG9Y29DwI2v9WhTxCkihAd5boTQz9eqrGB2luFiQoi2xeVvN12evDCiuVMkKQHPkz5fP49STP2Jsmh9CinRYmKbb9GSODrVAja2wqrlvyWbI3Ap7vTSlgc3wZvdYrHQb7tirl739b8EyprjjXp/PQzqzue18X1NUEzVhpy+mkp36RsUD0a1fUfAMst6j7a8QA5yrpGEK18JfZYKLBQ89ECtt .ssh/id_rsa $ ssh-add -D All identities removed. $ ssh-add .ssh/id_rsa .ssh/id_ecdsa Enter passphrase for .ssh/id_rsa: Identity added: .ssh/id_rsa (.ssh/id_rsa) Identity added: .ssh/id_ecdsa (.ssh/id_ecdsa) $ ssh-add -L ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCqmBxx8ghdl8mTB2fbfvoJLK16MOtf0SeE70D6zcp0mLxu9J2u4mUU91ME+VZIgxX2oE04oLRg+e8nJVgfoPjOiZx5bvm0IMdqiPPE8qu9eiqqLVU5M385/ckHRzr1qG9Y29DwI2v9WhTxCkihAd5boTQz9eqrGB2luFiQoi2xeVvN12evDCiuVMkKQHPkz5fP49STP2Jsmh9CinRYmKbb9GSODrVAja2wqrlvyWbI3Ap7vTSlgc3wZvdYrHQb7tirl739b8EyprjjXp/PQzqzue18X1NUEzVhpy+mkp36RsUD0a1fUfAMst6j7a8QA5yrpGEK18JfZYKLBQ89ECtt .ssh/id_rsa ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAM9ObyBQNDv5nBeVfTA8qTfaqAlHOSmHeTv5YmiHhhI5XTSnhc/mKItd1djQVCYUPYOSGuAzEJPRETamBH/kdE= .ssh/id_ecdsa
that's not what the documentation promises it says they will be all added and ~/.ssh/config should be respected in fact if i start it with "ssh-add .ssh/id_ecdsa .ssh/id_rsa" terminal programs will use ECDSA, in the reverted order they use RSA, well the main-problem here seems to be the idiotic rewrite of the KDE sftp-ioslave which does not support ECDSA at all *and* asks for the rsa-key-password even if the ssh-cli falls back to the RSA-Key in case a server does not support ECDSA in older KDE releases they used the openssh-clients via pipe and so implicitly supported anything of new openssh-releases while you now permanently have to verify that your configurations are working for CLI and GUI at the same time https://bugzilla.redhat.com/show_bug.cgi?id=1042833 throw away this crap and restore the pipe-behavior and please do not come again up with exuses about performance - the pipe in case of a networ protocol is *for sure* not the part responsible for performance
argh - wrong cross-refrence - sorry https://bugzilla.redhat.com/show_bug.cgi?id=1033370
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.
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.