Hello,

We just replaced a Windows 2K3 FTP server with an Ubuntu machine running vsftpd. Everything is working properly with the server except "ls" seems to work differently now than before. We post encrypted files named like so:

NAME.txt.pgp

While the server was W2K3, our clients were able to "ls N*.*.*" to retrieve the directory list. Now "ls N*.*.*" returns nothing but "ls N*.*" returns the correct list. I am hesitant to ask them to change their scripts because we were the ones initiating the server change.

Is there a setting I'm missing that could cause ls to work differently?

Thanks in advance!

Works for me with vsftpd 2.3.4 .. could it be a case sensitivity issue ?

Looks like I have 2.3.2. Wonder if there's a version difference - the first part of the filename is always uppercase, so I do not think that is the trouble. Here's an example, I FTP-ed in from the server itself:

ftp> quote PASV
227 Entering Passive Mode (127,0,1,1,21,95).
ftp> ls N*
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
-rwxrw-rw- 1 1002 1001 0 Feb 28 17:41 NAME1.txt.pgp
-rwxrw-rw- 1 1002 1001 0 Feb 28 17:41 NAME2.txt.pgp
226 Directory send OK.
ftp> ls N*.*
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
-rwxrw-rw- 1 1002 1001 0 Feb 28 17:41 NAME1.txt.pgp
-rwxrw-rw- 1 1002 1001 0 Feb 28 17:41 NAME2.txt.pgp
226 Directory send OK.
ftp> ls N*.*.*
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
226 Directory send OK.
ftp>

Exciting eh?

pasv_enable=YES is set in vsftpd.conf. Samba wouldn't do anything funny to these files/directories, would it? Typically the files themselves are posted to the server by Windows users.

Wierd, is the ftp directory actually on a samba share or local disk (ext3 .. etc)?

The FTP directory is local, sorry, I should have specified that.

It's probably a bug, there have been several glob bugs in vsftpd over the years - there's a relatively recent one (June 2011) here listed in an RHN Errata Alert but I can't see the details to confirm.

Thank you for checking the errata. I installed v. 2.3.5 but it had the same problem. Sigh. I'll try different software or (gasp!) ask the client to change their scripts.

FYI, it works with vsftpd-2.3.4 but not with 2.3.5, I guess because of the elevated security measures used in the last version. It also works with pure-ftpd and proftpd.
I would suggest to go with pure-ftpd if you don't want to force your clients changing their scripts

Regards

Great, thank you, I will try that.