FLOSS of the week: Filezilla server
Friday, June 27th, 2008Filezilla is pretty well known as an ftp client, but the project also includes an FTP server.
Currently available for Windows only, the server has a few advantages over the IIS ftp service:
- Security
The Filezilla interface is not tied into the Active Directory structure. While this may make some Windows admins groan, this does eliminate one potential source of compromises and intrusions, as it means that guessing a password on the ftp service doesn’t automatically give you a password for the actual machine that it’s running on. - Configuration
Configuration using Filezilla’s GUI is a bit hard to do at first, but the groups method is powerful. For example, define a group whose home directory is c:\ftp\:u, and then just create a directory of the same name as the user inside the c:\ftp directory (e.g. c:\ftp\simon.collis) and you put the user in that group, and they have a bespoke home directory - and they can’t do “cd ..” to get to other people’s home directories either, which can happen with IIS if you’re not careful! - Virtual file system
Unlike IIS, aliases show up in directory listings by default. You can also add other directories and map them - using my C:\ftp alias as above, to create a directory called shared everyone can see, simply add it in somewhere else - let’s say its real location is d:\ftp_shared. Add that in - either to the user or the group - and alias it to c:\ftp\shared. Now that directory shows up in the listings, and can be used just as if it were real. This is my only gripe, actually - that aliases are real directory names, not virtual ones. Makes working out what the filing system will be a bit confusing. - Bandwidth throttling
Filezilla can limit the bandwidth used by everyone, by a group, or by a user, for upload and download. So you can have “normal” users with a smaller limit, premium users with higher limits, and an admin with no limit at all! Of course, in IIS bandwidth throttling affects your websites as well - not the way to go about it if you’re trying to hosts websites on a server where more than one person will need to ftp in and out. This won’t be an issue for everybody, of course, and I’m sure there are those IIS experts who will say “just edit the metabase and everything will be fine”. Of course it will - but there’s only one global limit for IIS, not the user-level granularity you can have with Filezilla.
Filezilla users dialog: not eye candy, just well thought-outIn conclusion, if you’re looking for an alternative to IIS’s ftp service, not only is Filezilla robust and secure (I know of at least one production site making heavy use of it on a daily basis), the price is right and the feature set is probably just what the doctor ordered!
(PS: I’m thinking about doing this every Friday - highlight a piece of free or open source software I think you’ll find useful or enjoyable. Is that a good idea or not? Let me know in the comments…)


