https://bugzilla.novell.com/show_bug.cgi?id=635630 https://bugzilla.novell.com/show_bug.cgi?id=635630#c0 Summary: VsFTPd not using correct configuration if user connected to server name with DNS A record, including failure to chroot user Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team@suse.de ReportedBy: dank@kth.se QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=386318) --> (http://bugzilla.novell.com/attachment.cgi?id=386318) config file for vsftpd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 I have a machine running a FTP server using "ftp.example.com", but the same machine also hosts various other things like web services. The ftp-subdomain is an A record in the DNS. For mostly cosmetic reasons I've also created two CNAME records (to ftp), www and test. Thus one can actually FTP to "ftp.example.com", "www.example.com", "test.example.com", or directly to the IP address (of course). It is the same daemon instance of VsFTPd that answers (that's correct). I've set up VsFTPd to chroot non-admin users to their home dir, this also works fine... in most cases. When connecting on any of the "CNAME names"/IPs that the machine responds to, the same user IS chrooted, exactly the way I would expect. However, when connecting to "ftp.example.com" (the A record), the user is NOT chrooted and can browse the whole file system. I first thought it was only the chroot that failed, but after more testing it seems perhaps the whole VsFTPd config is wrong for users in the "A record name" case. For instance, I've configured VsFTPd to log to its own log file (not the system log), and this also works correctly for all "other" cases, but the "A record name" case fails - nothing is written to the log file. Reproducible: Always Steps to Reproduce: 1. Use a computer with an IP bound to a DNS A record name, plus any number of CNAME record aliases to the A record name. 2. Setup VsFTPd with the config attached (listening to all interfaces/names). 3. Create a user to be chrooted to its home and make sure it is NOT listed in the vsftpd.chroot_list file. 4. Run/restart VsFTPd 5. Use a FTP client to connect to the FTP server on the "A record name". Optional: 6. Use a FTP client to connect to the FTP server on a "CNAME record name" or IP address. Notice the correct behavior. Actual Results: The user is NOT chrooted. Also that the FTP access was NOT logged in the /var/log/vsftpd.log file. Expected Results: The user IS chrooted correctly to its home. Also that the FTP access was logged correctly in the /var/log/vsftpd.log file. All the latest updates are installed. However, I think I saw this problem before upgrading to 11.3 (on 11.2) but at that time I didnt bother to investigate further. uname -a: Linux myserver 2.6.34-12-xen #1 SMP 2010-06-29 02:39:08 +0200 x86_64 x86_64 x86_64 GNU/Linux VsFTPd version: 2.2.2-2.4 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.