I am trying to create a new secondary user that has access to SFTP files and SSH access to a specific directory.
I have the SFTP work, but when I try to login via SSH, I get the following error: Write failed: Broken pipe
The root user uses a public/private key, but I want the secondary user to use a password.
Here is what I have so far:
useradd test
passwd test
usermod -G www-data test
usermod -d /usr/share/nginx/html test
chown test:www-data /usr/share/nginx/html
As for additions to my sshd_config
:
AllowUsers test
Match User test
ChrootDirectory /usr/share/nginx/html
PasswordAuthentication yes
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
All I have left todo is to get the test user to be able access the CLI in their home directory to run composer and artisan commands.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
By adding
ForceCommand internal-sftp
you block any access the user would have to any form of CLI, shell or terminal session. In fact, you’ll even ban SCP usage in favor of only sFTP.If your run
sftp test@xxx.xxx.xxx.xxx
you will currently be able to list files and navigate the chroot jail and depending on permissions, read or read and write.Does your user need a direct she’ll or is sFTP sufficient?
On RHEL dont work :(
I executed
And the new user still can navigate to any folder outside /usr/share/nginx/html