Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
022 will work, however 0022 is more correct since the man page says that all octal values must be preceeded by a zero. So, those of you that try using a different value, such as local_umask=222 are gonna be in for a rude suprise when the 222 is read as a decimal 222 and converted to 336 octal. The correct usage would be local_umask=0222. By using the four digit values all the time any future confusion can be avoided.
Also, don't forget that there is a default file_open_mode=0666 if you don't specify one in your config file. This will affect the default file permissions as well.
I want to set up an anonymous read-only vsftpd server where only a single upload folder is writeable. Uploading folders is fine, but files get the wrong permissions. My setup looks like this:
I have the user "ftp" with a home folder of /home/ftp which looks like this:
Code:
Superfly ftp # ls -a
total 12
dr-xr-xr-x 3 ftp users 4096 Jan 29 20:21 .
drwxr-xr-x 6 root root 4096 Jan 28 19:38 ..
drwxrwxr-x 4 ftp users 4096 Jan 29 20:47 upload
The upload folder looks like this:
Code:
Superfly ftp # ls upload/
total 56
-rw------- 1 godji users 2 Jan 29 19:12 hello.txt
-rw------- 1 godji users 453 Jan 29 20:02 m.txt
-rw------- 1 godji users 453 Jan 29 19:42 mm.txt
-rw------- 1 godji users 453 Jan 29 19:51 mm2.txt
-rw------- 1 godji users 453 Jan 29 20:26 mmmmmm.txt
-rw------- 1 godji users 453 Jan 29 19:59 mmt.txt
-rw------- 1 godji users 453 Jan 29 20:40 n.txt
-rw------- 1 godji users 453 Jan 29 20:44 n1.txt
-rw------- 1 godji users 453 Jan 29 20:47 n2.txt
-rw------- 1 godji users 2 Jan 29 19:25 argh.txt
drwxr-xr-x 2 ftp users 4096 Jan 29 20:38 test
-rw------- 1 godji users 2 Jan 29 09:48 test.txt
drwxrwxr-x 2 ftp users 4096 Jan 29 20:39 test2
-rw------- 1 godji users 2 Jan 29 19:13 wee.txt
All .txt files have been uploaded by an anonymous client. I want them automatically transferred to the "godji" user (my daily account) so that I can easily move them away from KDE. I'm aiming at "-rw-rw-r--". My vsftpd.conf is the following:
I've been looking around the web but most problems are solved by either setting anon_umask or file_open_mode the way I have them. Please help if you can!
Godji, I'm experiencing the same problem you are. I've got anon_umask=0022, file_open_mode=0666, and have tried several variations on that with no success. Every file that gets uploaded via anonymous ftp has file permissions of 600.
I've read on some sites that this is a but in vsftpd, but I can't find either confirmtation or a fix. This concerns me because some of the tentative bug reports date back over a year.
If anyone has more concrete information, I'd appreciate getting this addressed.
could someone please explian why sometimes its local_unmask=0xx (2) and other people have it as local_unmask=0xxx (3)
Yes, please I need the explanation also.
The documentation in vsftpd.conf says change to: local_umask=022 which is not working for me. My client is trying to set the permission to 533 and it says that it failed to do that.
022 will work, however 0022 is more correct since the man page says that all octal values must be preceeded by a zero. So, those of you that try using a different value, such as local_umask=222 are gonna be in for a rude suprise when the 222 is read as a decimal 222 and converted to 336 octal. The correct usage would be local_umask=0222. By using the four digit values all the time any future confusion can be avoided.
Also, don't forget that there is a default file_open_mode=0666 if you don't specify one in your config file. This will affect the default file permissions as well.
THANK-YOU rbrightwell!! The permissions being preceded by the 0 was what was throwing my setting off!
If you have used the options chown_uploads=YES, chown_username=someuser then anon_umask will not used to determine the permissions of anonymously uploaded files. Use "chown_upload_mode" option to set anonymously uploaded files. as in below;
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Permission Information
