Skip to content

uFTP 4.2.0 release notes

Changes since 4.1.0: a round of hardening and reliability work. Upgrading is recommended.

Hardening

  • Clients that have not logged in no longer hold connection slots, and users stay inside their home directory.
  • Better protection of the TLS session, of data connections and of the login lock-out (now also for IPv6).

Improvements

  • FTPS: downloads with FileZilla and other strict clients end cleanly.
  • Transfers: a failed upload or download is reported as failed, slow links are handled better, and parallel uploads into a directory that is still being created get a temporary 450, so clients retry.
  • Protocol: reply codes follow the FTP RFCs more closely, and HELP and ALLO are available.
  • Logs: they now say what happened: startup, restarts, logins, transfers and why each connection closed.

New options

Option Default Purpose
LOGIN_TIMEOUT 60 Seconds allowed to complete the login (0 = no limit)
PASV_PROMISCUOUS false Accept passive data connections from any address
RESPAWN_PROCESS true Restart the server automatically if it stops

Upgrading

  • Clients log in within 60 seconds, and data connections come from the client's own address (PASV_PROMISCUOUS = true behind NAT pools).
  • Symbolic links that point outside the home are no longer followed.
  • An upload into a missing directory answers 450 (was 550) and an interrupted download 426 (was 550).
  • The sample uftpd.cfg is meant as a starting point: replace the sample users, use dedicated home directories and force TLS.