workaround/fix:
- move all keys into subdirectories and update config to reflect changes.
- even with multiple keys in subdirectories it does not try the wrong keys.
hypothesis:
- the ssh client looks in ~/.ssh and tries any files it deems to be keys, even when 'config' is configured explicitly with the appropriate key. Fortunately, it does not recurse into subdirs.n
other observations:
- the behaviour persists without a config file and specifying the key on the command line (ie. ssh -i keyfile host)
- this fixes putty, also (must have been patched to use ~/.ssh at some time)
workaround/fix:
- move all keys into subdirectories and update config to reflect changes.
- even with multiple keys in subdirectories it does not try the wrong keys.
hypothesis:
- the ssh client looks in ~/.ssh and tries any files it deems to be keys, even when 'config' is configured explicitly with the appropriate key. Fortunately, it does not recurse into subdirs.n
other observations:
- the behaviour persists without a config file and specifying the key on the command line (ie. ssh -i keyfile host)
- this fixes putty, also (must have been patched to use ~/.ssh at some time)