![]() ![]() # Uncomment this if you want the anonymous FTP user to be able to create # obviously need to create a directory writable by the FTP user. # has an effect if the above global write enable is activated. # Uncomment this to allow the anonymous FTP user to upload files. # if your users expect that (022 is used by most other ftpd's) # Uncomment this to enable any form of FTP write command. # Uncomment this to allow local users to log in. # Allow anonymous FTP? (Beware - allowed by default if you comment this out).anonymous_enable=NO # Please read the nf.5 manual page to get a full idea of vsftpd's # READ THIS: This example file is NOT an exhaustive list of vsftpd options. # Please see nf.5 for all compiled in defaults. # loosens things up a bit, to make the ftp daemon more usable. # The default compiled in settings are fairly paranoid. Here's an example config from my working system that chroots users to a directory structure: # Example config file /etc/vsftpd/nf I've had issue setting up vsftpd before (it can be finicky). ![]() If you really really need full system access and need native permissions setup and ease of use, checkout SCP login, which logs in using SSH (secure) and the user is limited to whatever permissions you setup in the filesystem (same user as is in /etc/passwd). that is quite dangerous and you may come to regret it one day (FTP is extremely insecure and by default sends credentials over plain text - if you enable the SSL wrapper then it is much more secure, but still having full system FTP access is not great). but - try taking a loot at /var/log/vsftpd.log and see what happens when a user tries to create a directory inside their chrooted directory (/var/Also, I hope you are chrooting the users, and not granting full system FTP access. I don't know if the SSHD ftp subsystem allows for chrooting user to a specific directory or not. ![]()
0 Comments
Leave a Reply. |