Closed adripo closed 4 years ago
Hi @adripo - I need to check the code but if I remember correctly it skips the ownership change. You should still be able to access the folder if the user has access (depends on the source folder permissions). Have you tried connecting and seeing if you can access the contents?
Yes, I checked and everything work correctly. I was wondering if this is the right way to do it, or if I have to let the sftp folder writeable and bind my ro folder inside sftp. Would this be a better solution?
@adripo No, if you just want the user to have RO access, that is the correct way because otherwise you will disclose what the other users have in their homes. I'll see if in the new version I can include a more comprehensive message.
Thank you!
I created the user
public
insidesftp.json
and binded the volume on docker run with this option-v /host/Public:/home/public/sftp:ro \
Please note the :ro option.
After running it, in the log of the container I find this exception
Is there any other way to set a read only folder for a user? Am I doing something wrong?