https://bugzilla.mindrot.org/show_bug.cgi?id=2709
--- Comment #2 from Clay Gerrard <[email protected]> --- You're probably right. But please consider... Unlike ENOENT - the permissions error is not really an expected normal condition. Consider when the permissions are *too* permissive: Jun 2 16:05:44 localhost sshd[3343]: Authentication refused: bad ownership or modes for file /home/ubuntu/.ssh/authorized_keys Or this message when the file is a directory: Jun 2 16:14:17 localhost sshd[3421]: User ubuntu authorized keys /home/ubuntu/.ssh/authorized_keys is not a regular file Where as when the user/owner is wrong (which causes an error trying to read the file) - AFAICT there is no helpful/clarifying message printed unless the log level is DEBUG. Which is *fine* - but I think this EPERM is hardly something you would expect to be any more unlikely/common than the file's mode, or it being a non-regular file. OTOH, if there was some more esoteric error reading the file.... well that might be *very* interesting/noteworthy. /me shrugs Thanks for the response and suggested doc patch, very helpful/responsive. I appreciate your maintenance/service. Thank you! -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
