rottame
committed
about 1 year ago
(revision 1)
- update to 1.0.51:
* Compatibility with OpenSSL 1.1.0 was improved.
* PostgreSQL: the port number is not escaped any more in connection
strings.
* TLS tickets are issued but not renewed - This fixes compatibility
issues with some clients.
* PureDB: additional checks for corrupted databases have been added,
and synchronization to disk uses F_FULLFSYNC on macOS X.
- Update to version 1.0.50:
* Support for MD5, SHA1 and MySQL PASSWORD() function were removed for
password hashing. You should now use scrypt, argon2 or the system crypt(3)
function.
* Soft fail if a USER command is received without TLS and the server is
configured to enforce TLS. Previously, the session was immediately closed,
but that was too brutal for some clients.
* Allow connections from the class E network range -- apparently
required in some cases when using Linux containers.
* Large file listings used to require way more stack allocations than
necessary, possibly reaching hard-coded limits and causing a forced
session close. This has been fixed. (boo#1160111, CVE-2019-20176)
* The SPSV command has been removed.
* Under some circunstances, the server would not start when configured
with directory aliases. This has been fixed.
* PostgreSQL: hard-coded global configuration strings were not escaped.
This has been fixed.
* A warning is now printed when a transfer happens in ASCII mode, as
this is rarely intentional.
* Compilation with --without-ascii is now possible again.
* Configuration options for features that have been disabled at