-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Public key authentication not working in version 3 #22
Comments
v2.1.14 will work, permissions of users' home folder on v3 prevent sshd from reading the authorized_keys file using a custom |
@winromulus two possible solutions here, either move authorized_keys out of users' home, or create the home directory with 755 permissions. |
me not understanding SFTP chroot permissionsWhy is the users home directory owned by In fact, nearly everything is owned by
|
@antoinedeschenes @josefschabasser I'm currently investigating this @antoinedeschenes - Not sure if creating the home directory with 755 will work because of chroot. |
Yes, the sshd auth process runs unprivileged and can't reach the authorized_keys file |
@antoinedeschenes - I think this is a breaking change after setting the container to run as a non-root user. |
After doing a lot of research I've concluded that the current version of sshd cannot run unprivileged without affecting multiple capabilities, authorized keys being one of them. I'm putting in a new PR to run the container as root again. |
Hello everyone, I am getting the same error even with version docker-compose.yaml:
config.json:
Am I missing anything here? |
@tibarix feature was added in 2.0.12 |
@winromulus aren't we already running as root?
The problem seems to be the auth process (PID 221 in this example) not having access to the users' home folder |
@antoinedeschenes I apologise. I did a lot of work that weekend and was under the impression that I modified this project to run as non-root (was thinking of the Reflector project). |
@antoinedeschenes @josefschabasser - Fixed the issue by setting home directory permissions to 711. |
Hi!
I set up emberstack/sftp as an Azure container Instance. I tried to configure public key authentication, but as soon as I set the password to
""
ornull
I can't login anymore.Here is my configuration:
Log output when using
sshfs
:When I use Filezilla, more or less the same thing happens.
EDIT: shortened log
The text was updated successfully, but these errors were encountered: