Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 89517 - Vsftpd and default ftp file permissions
Vsftpd and default ftp file permissions
Product: Red Hat Linux
Classification: Retired
Component: vsftpd (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-04-23 14:43 EDT by Nickel
Modified: 2007-04-18 12:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-14 09:22:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nickel 2003-04-23 14:43:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
I am using vsftpd as my ftp daemon for my web server. The accounts on the 
system are strictly for ftp access, users have no telnet or ssh access to the 
server. In the vsftpd.conf I have anon_umask and local_umask set to 003, which 
should allow 774 permission. But every file that is ftp'd to the serve is set 
to 664. I do not understand what is overriding the vsftpd umask settings. Any 
information would be much appreciated.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Make umask changes to vsftpd.conf
2.Completly kill and then restart xinetd to reload vsftpd 
3.upload a file to the server. Run an ls -al on the file and it returns 664 

Additional info:
Comment 1 Radek Vokal 2004-08-23 03:47:11 EDT
Hi Nickel, may I have your vsftpd.conf file? Also can u please check
if the bug appears for vsftpd-2.0.1 (It doesn't for me)
Comment 2 Radek Vokal 2004-09-16 04:57:41 EDT
Check file_open_mode configuration - The permissions with which
uploaded files are created.

Note You need to log in before you can comment on or make changes to this bug.