Hey friend,

Great question! You can have them generate their own SSH key and then add their public key to your authorizedkeys file on the droplet (/home/user/.ssh or /root/.ssh). If you need them to have root access, note that while you can remove their SSH public key from the authorizedkeys file at any time, there may be no way to know what backdoors they’ve left for themselves. Never let anyone you don’t trust in with root or sudo access.

Setting up a privileged user with only access to what they need makes more sense, but there’s no one size fits all instruction for doing it because every situation varies. For example, needing them to access a folder will be different than needing them to read/write a folder that is also able to be read/written by an active service.

Jarland

I followed the recipe that unixynet linked to. However, I am running into some obstacles. I want to give somebody access for technical support so he would need the full rights to a website (but not the other on this server). The example creates a special directory and gives the visitor its ownership but that is no option for me. I need to give full rights to something of which the visitor is not the owner.

What I did now was:

• adduser visitor

And then I have adapted the /etc/ssh/sshd_config file by adding:

Match User visitor
ForceCommand internal-sftp
PasswordAuthentication yes
ChrootDirectory /home/mysite/public_html
PermitTunnel no
AllowAgentForwarding no
AllowTcpForwarding no
X11Forwarding no

I can connect in FTP with the user’s name and password but then it gives an error message that it cannot retrieve the folders