[Bug 2700] Missing PEM identity_file should be a fatal error

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Mon Mar 27 17:36:41 AEDT 2017


Darren Tucker <dtucker at zip.com.au> changed:

           What    |Removed                     |Added
                 CC|                            |dtucker at zip.com.au

--- Comment #1 from Darren Tucker <dtucker at zip.com.au> ---
(In reply to jg from comment #0)
> ssh -i "me.pem" ubuntu at myserver33.net
> My thought is that this should be a fatal error, not just a warning.

Well the connection may be able to succeed via some other key (eg from
an agent) or via another auth method (the client doesn't know what
methods the server will offer when it's parsing options).

As for whether a missing/unreadable key file should be a fatal error,
I'm not sure.  I can imagine it breaking otherwise working configs.

> Another note, the error is not accurate, as only a file is expected.
> ie if open() on the file fails, errno is ENOENT, then it should say
> "No such file"

ENOENT is not that specific.  If you specify a non-existent directory
(eg -i "/no/such/id") in which case that message would be wrong.

You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

More information about the openssh-bugs mailing list