- Professional FTP Daemon -

 

Current Development State

The ProFTPD source tree is managed via CVS (Concurrent Versions System). While there may be a large number of branches in the CVS tree, the actual tarball release of ProFTPD is boiled down into four flavors:
  • Production Release
    The production release is a "stable" version, most suited for conservative administrators. It is less likely to have as many features as development releases as well as less bugs.
  • Production Release (incremental patchlevel)
    Released between maintenance versions, each patchlevel will address one or more bug fixes which are slated for rollup into a new maintenance production release.
  • Development Release
    Development releases are bleeding edge version of ProFTPD, in which the latest and greatest features ("unwanted" features included) are being worked on.
  • Development Release (incremental patchlevel)
    These releases contain specific feature sets and bug fixes which are slated for an upcoming development release.

You can FTP the latest and greatest production or development release (and patchlevels) from the ProFTPD download page. Because the web site may lag slightly behind actual development work, you can finger proftpd@proftpd.org for the latest version information.

Version Numbering

ProFTPD version numbers are in the format: major.minor.maintenace[pl[patchlevel]]

Minor version numbers are odd for development releases, and even for production releases. Incremental patchlevel releases are always "later" in the source tree that the maintenance release they are based on. The RCS revision numbers found at the top of source and header files (the $Id tag) are NOT related to actual release versioning, and are handled completely by CVS without human intervention. Don't rely on them to tell you anything (unless you are a developer).

Bug Reports and Current Bugs

All bugs reports should be submitted to bugs@proftpd.org.A patch to fix the undesired feature in question would be very appreciated (if possible). If you're interested in taking an active role in ProFTPD development (your ego will be stroked tremendously as compensation), please contact flood@proftpd.org.
Date Version Severity Description
10/12/97 0.99.0pl7 Wishlist ProFTPD does not support the non-RFC (yet, defacto standard) MDTM command (MoDification TiMe). Added in 0.99.pl8.
10/12/97 0.99.0pl7 Moderate Occasional "Invalid PORT command." errors when transfering large numbers of files. Fixed in 0.99.0pl8.
10/12/97 0.99.0pl7 Severe Long ASCII mode transfers occasionally cause the proftpd daemon to seg fault (crash). Notably, this occurs when retrieving extremely large directory listings. Fixed in 0.99.0pl8.
08/01/97 0.99.0pl6 Moderate Entries in the wtmp log (seen via 'last') appear to never log out, and appear to be logged in from terminal 'ftpXXXX' (where XXXX represents the PID of the proftpd process the user is logged in under). Fixed in 0.99.0pl7.
08/01/97 0.99.0pl6 Severe Two "infinite loop" bugs: One caused by an inability to handle recursive symlinks, another due to possible I/O deadlocking if a remote connection gets dropped at the wrong time. Fixed in 0.99.0pl7.
06/20/97 0.99.0pl5 Moderate A known symlink problem exists involving proftpd's inability to determine the current working directory if a symlink takes a client to a directory where one or more upper level directories permissions deny 'x' access. Notably wsftp95 has problems in this area. Fixed in 0.99.0pl6.
06/20/97 0.99.0pl5 Moderate Proftpd may unexpectedly close connections when transfering _large_ numbers of files over a FAST network connection (LAN). The symptoms of this bug are syslog messages along the lines of: "bind() failed in inet_create_connection()". Fixed in 0.99.0pl7.
06/02/97 0.99.0pl3 Severe Restarted file transfer (via the REST command) causes subsequent transfers to SIGSEGV the server. Disable REST via <Limit> as a temporary work-around. Fixed in 0.99.0pl4.