1

I have a server which enables some users of my services to upload files using SFTP. When I talk about users, I can neither be sure who they are nor how many have access.

I have set up the access as follows:

  • SFTP (SSH) access with username and password: PasswordAuthentication yes.
  • Users belong to the group sftp which is forced to use internal-sftp.
  • Login is sandboxed to ChrootDirectory %h which is /srv/sftp/incoming.
  • Login Shell is /bin/false.

Is there anything else I can do to secure an SFTP access for a such a range of users?

The machine runs ArchLinux. Webserver is nginx but the files in /srv/sftp/incoming are not served by the webserver. It's just for internal use.

  • Remove the read access on incoming folder and remove the list permission, to be sure a document title are hidden from other uploader – yagmoth555 Apr 16 '16 at 14:34
3

You can set-up SSH keys to every user, so they have to use private key to get access to SFTP server. Let clients generate private and public key by themselves and let them send public key to you, so you can add it to ~/.ssh/authorized_keys file.

You can generate private and public key ofcourse by yourself but that means you need to send private key to client somehow, what makes it unsecure.

ssh-keygen -t rsa

When key's are set-up you can disable password login at /etc/ssh/sshd_config so they have to use private key to get access to server.

PasswordAuthentication no

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.