Bad `authorized_keys` is not reported in non-debug mode about dropbear HOT 5 OPEN

It should print a message with the filename

Checking here:

[3151192] Dec 11 23:09:45 /home/matt/.ssh/authorized_keys must be owned by user or root, and not writable by group or others

from dropbear.

Right, I checked again now. dropbear -E -s -F -r ... -w -g -a -p 2222 -P ... warns for permissions of authorized_keys.

It does not warn for non-existent authorized_keys. Please consider if this warrants a warning, because I infer from -s, as a newbie, that there is no other auth method possible besides password and key?

I am otherwise fine with this. Thank you for looking into it.

from dropbear.

The problem is that it would print a warning for every user who is just logging in with a password, who doesn't have an authorized_keys file.

from dropbear.

But if -s is passed (Disable password logins) and authorized_keys does not exist, the server is unusable?

from dropbear.

It is for a non-root dropbear, sorry for not clarifying earlier. The context is my unprivileged container use case described here, so a single-user server + clients who run apps in the same sandbox and the same UID as the server.

from dropbear.