Hot answers tagged


Yes it probably does use mkdir(2) and open(2) (or something very similar). You could check by running strace(1) on your ftp daemon and exercising it e.g. strace -p <pid of ftp daemon>


It most probably means that the /usr/lib/openssh/sftp-server does not exist. Make sure the Subsystem directive points to an existing path: Subsystem sftp /usr/lib/openssh/sftp-server Or actually, nowadays you typically use the internal-sftp instead: Subsystem sftp internal-sftp See OpenSSH: Difference between internal-sftp and sftp-server.


You have got typo in the sshd_config: Subsystem sftp intenal-sftp should be Subsystem sftp internal-sftp


I think you don't need vsftpd server at all. OpenSSH server allows you to upload files using sftp. You configured vsftpd as ssl enabled ftp server (ftps). read more Also you can improve your server security using next simple steps: move ssh server to another port ex.Port 422; set PasswordAuthentication no use ssh keys only; setup firewall (for example ...


No, it is not safe to configure your firewall as you indicated. Using a firewall configured using the rule in the image you linked would be a security risk because that rule effectively opens up ALL ports and all protocols. The reason your port 21 rule was not working was because FTP actually requires 2 channels to function, a command channel and a data ...


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 ...

Only top voted, non community-wiki answers of a minimum length are eligible