Maintenance release: Syncplify.me Server! v3.1.20.60

We have just released version 3.1.20.60 of our Syncplify.me Server!

This new maintenance release fixes a bug in the AppendStringToFile function of the event-handling scripting framework. This update is not necessary if you aren’t running scripts containing the above mentioned function.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.19.59

We have just released version 3.1.19.59 of our Syncplify.me Server!

This new maintenance release fixes a bug in the AVBL command that was affecting the FTP protocol family only (SFTP was not affected). Thanks to Martin for identifying and reporting this issue.

As usual you can download the latest version from our web site. Thank you!

Clarification: W3C log file format and UTC timestamps

Syncplify.me Server! version: 1.0.0+

Every once in a while we receive a support request from some customer asking us how to “fix” the timestamp in the log files, because it’s few hours ahead/behind.

The thing is that such timestamp is not ahead nor behind: it’s always in UTC (Coordinated Universal Time), and that is not our arbitrary choice; in fact, the W3C Extended Log File Format official working document clearly states that the timestamp must refer to the GMT time zone without daylight savings bias, which is – indeed – called UTC for brevity.

For such reason, all existing log analysis software products are designed to take that into account and adapt the generated reports to the current time zone of the machine that runs the analysis.

Continue reading

Firewalls and FTP external IP address for PASV

Yesterday we came across what, at first, seemed to be a pretty odd case, and we think it’s worth sharing it with our users.

Most firewalls (we’d say all the ones we know) have NAT/PAT capabilities, and many are able to perform protocol-level inspection when the connection is not encrypted. SSH (and SFTP) are always encrypted, but FTP can be either encrypted or not; yet, theoretically protocol inspection should only prevent protocol-related attacks, not modify client requests or server responses.

Yet, yesterday a customer with a perfectly configured instance of Syncplify.me Server! was experiencing a weird behavior: FTPS/FTPES (encrypted) sessions were working perfectly, while plain FTP sessions were dropped upon every attempt to open a data connection to transfer files. Continue reading

Maintenance release: Syncplify.me Server! v3.1.12.52

We have just released Syncplify.me Server! v3.1.12.52, a maintenance release that comes with the following improvements and new features:

  • User profile automatic expiration date can now be set via CLI (command-line interface)
  • A tiny memory leak in the logging subsystem has been fixed
  • Send buffer performance improved in critically slow network conditions

In order to set the expiration date using the CLI, you have to pass the date to the -autoexp parameter in RFC959 format (YYYYMMDDHHmmSS, no spaces). Here’s an example that will set the expiation date for a user at noon on Christmas day 2015:

Passing any parameter in a format other than the RFC959 date format specified here above, will disable the automatic expiration of the user profile. The following commands all disable the automatic expiration:

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.6.46

We have just released Syncplify.me Server! v3.1.6.46 to work around the issues caused by CloudBerry Backup, as discussed in this post.

The SFTP protocol standard states “The server will respond to this request with a SSH_FXP_STATUS message. If a file or directory with the specified path already exists, an error will be returned.”; Yet, CloudBerry Backup tries to create the same directory twice and when Syncplify.me Server! correctly sends an error back the second time (because the directory already exists) CloudBerry Backup (3.9.6.42) considers the backup job failed.

This new version of Syncplify.me Server! tries to identify CloudBerry Backup, and sends a “success” reply upon double directory creation requests, but will practically ignore the second request if the first one was successful.

We have already contacted CloudBerry Lab, and we will remove this workaround from our software as soon as they release an update that fixes their protocol violation issue.

For now, if you need to use Syncplify.me Server! together with CloudBerry Backup, you are advised to download the latest version of our server from our web site.

Maintenance release: Syncplify.me Server! v3.1.3.43

We have just released a maintenance update to our Syncplify.me Server! with the version number 3.1.3.43. This new update delivers the following:

  • fixed a minor bug in the message code that was sent to the client upon accessing a locked file (only over FTP protocol family)
  • added a “Test SMTP Configuration” button to the Configuration Manager

As usual, you can download the latest version from our web site.

New release: Syncplify.me Server! v3.1.0.40

We have just released Syncplify.me Server! v3.1.0.40. This new version fixes/adds the following:

  • Fixed a bug that prevented the correct encoding of dates and times in FTP file listings on operating system locales other than English
  • Fixed few glitches in the Configuration Manager
  • Added color-coding to both command-line components
  • Added custom SendToClient function to the scripting subsystem (only for FTP/S protocols)

As usual you can download the new version from our web site.

New release: Syncplify.me Server! v3.0.3.33 (minor fix)

We just released v3.0.3.33 of our Syncplify.me Server! software.

This version only fixes a small glitch with Windows/AD user management, where it wasn’t possible to apply multi-factor authentication to such profiles (the field in the Configuration Manager was erroneously disabled).

As usual, you can download the new version here. Thank you for your support!

New release: Syncplify.me Server! v2.0.6.26

While our customers are eagerly waiting for the upcoming new version 3 of Syncplify.me Server!, we do not underestimate the importance of supporting the existing version 2. Therefore we have released Syncplify.me Server! v2.0.6.26 today.

Here’s a short list of what’s fixed or new in the new version:

  • Fixed: compatibility issue with FileZilla Client
  • New: configuration of external IP for PASV connections (when behind NAT)

As usual you can download the updated version here.