Yes indeed, this is a bug in edtFTPD v0.9.2. I don't know how that one slipped through.
This bug will be fixed in 0.9.3, which is due to be released soon. The release will be announced in the edtftp.server.technical and edtftp.announce forums.
EDT Support.