Syncplify Server! v6.0.27 released 🚨

Importance of this update: VERY IMPORTANT
Fixed
  • HAProxy headers now report the correct client IP address in the SSH2/SCP/SFTP protocol handler
  • Importers (V4/V5) now auto-sanitize all IP/Network lists by removing incorrect items
Improved
  • Decreased heap memory allocation by ~0.8%
  • Sped up file transfers by ~1.4%
  • Upgraded SyngoDB to v4.5.5
  • Radically changed validation for all APIs and database objects/structures: now anything that can be sanitized (auto-corrected) will be sanitized, and validation errors will be reported only for those rare cases in which automatic sanitization is not possible: this should reduce the number of errors returned by the Admin UI upon saving configuration changes by up to 95%
  • Most of the remaining errors are now reported with clear messages in plain English
  • Removed nearly all null values from JSON objects returned by the APIs

Upgrading from v6.0.x is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!


JSON structured logs

Log files are system administrators’ best friends. Well, they are if they are understandable and useful. The problem with most log files, including most of the so-called “human-readable” ones, are very badly structured, and ultimately only truly understandable by a machine.

For that reason, in the past few years JSON-structured log files have become all the rage. Because they are easily understandable by a human being, and extremely fast to parse for a computerized log analyzer.

So, yes, in Syncplify Server! v6 you will find JSON-structured logs that look pretty much like this:

{
    "time":"2021-06-18 13:31:46.781",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"SESSION-START",
    "uriStem":"",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }{
    "time":"2021-06-18 13:31:46.786",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"LIST",
    "uriStem":"/",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }{
    "time":"2021-06-18 13:31:48.257",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"SESSION-END",
    "uriStem":"",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }

In addition to that, while older versions of our software only supported logging to file or syslog, the next major version will support 4 log targets: file, syslog, database, or stdout.