Explicit identity files are being used after implicit files are attempted
Bug #1302812 reported by
Michael Hall
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
portable OpenSSH |
Invalid
|
Low
|
|||
gnome-keyring (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
openssh (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When explicitly setting an identity, either via the -i commandline parameter or IdentityFile in the ssh config, these files are used only after any other identity files found in ~/.ssh/ have failed pubkey authentication.
When the remote host limits the number of pubkey authentication failures before disconnecting, this can lead to a situation where the explicit identity file is not even used when connecting to that host.
Changed in openssh: | |
importance: | Unknown → Low |
status: | Unknown → Invalid |
To post a comment you must log in.
When explicitly setting an identity, either via the -i commandline parameter or IdentityFile in the ssh config, these files are used only after any other identity files found in ~/.ssh/ have failed pubkey authentication.
When the remote host limits the number of pubkey authentication failures before disconnecting, this can lead to a situation where the explicit identity file is not even used when connecting to that host.