1 List of known bugs and problems:
2 - Some commands are still not implemented (see the file RFC-COMPLIANCE). There
3 are very few I actually miss now... None, actually.
4 - There are several hardcoded limits, instead of using constants such as
6 - We should move the remaining bugs listed from the source (in the comments)
8 - If a command that requires a parameter doesn't have one, BetaFTPD will send
9 500 instead of 501. This behaviour is very useful in the command lookup
10 (for code simplicity) :-)
11 - We could (perhaps) use a hash table instead of a straight linear command search?
12 - REST does not work in ASCII mode. (This is partly as a security measure --
13 enabling resuming on ASCII files could need a lot of CPU power if we had to
14 resume in the middle of a big file, and still stay RFC/ftpext-compliant.)
15 - In general, nonroot support has problems. For instance, security is generally
16 weak, and anonymous FTP is not supported (all users will need a password).
17 Nonroot is not even worked on at the moment. Don't use it :-)
18 - Occasionally, a directory listing may cause unwanted output in the fullscreen
19 mode, for some weird reason.
20 - There are reports of the server not working at all in fullscreen mode. We're
21 working to find and fix these problems.
22 - Some features like ftpshut and ftpaccess files (no, root can't FTP anymore,
23 that is blocked) are missing.
25 Obscure bugs I haven't seen in a long time (probably fixed):
26 - The server is still known to segfault from time to time, but unfortunately,
27 most kernel versions won't dump core if the program has changed uid :-(
28 - Sometimes (after an error) the server doesn't respond to the connection
30 - Some times, for no reason at all, mmap() on my machine will fail with a
31 EINPROGRESS, which is a non-legal error code. I'm not sure if this is
32 a bug in BetaFTPD or glibc :-)