Syncplify Server! v6.0.16 released

Today we released Syncplify Server! v6.0.16; here’s what’s new and improved in this version.

Importance of this update: MINOR
Fixed
  • Glitch in the Admin UI that affected only the Linux version preventing it from using standard POSIX paths when creating new VFSs

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!


Syncplify Server! v6.0.6 released

Today we released Syncplify Server! v6.0.6; here’s what’s new and improved in this version.

Fixed
  • If an Admin profile was incompletely imported from an old backup, all Admin profiles of that virtual site would be non-editable
  • The list of VFS selectable as Home-VFS for a User profile was limited to 20 items
Improved
  • Restore/import functions from old V4/V5 backups have been further improved
  • Re-activation of the same license on the same “system ID” can now be performed autonomously by the SuperAdmin

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!


For those who use(d) DiskAES256 VFSs

The DiskAES256 virtual file system (VFS) type provided at-rest encryption in Syncplify.me Server! v4.x and v5.x, and served its purpose well for several years, but it got old, and in IT lingo “old” means that it can’t be considered secure anymore. It uses the AES-256 algorithm in a simplified version of the XTS mode, so we decided to retire it while it’s still unbroken.

In fact, at-rest encryption in Syncplify Server! v6.x will be provided by a state-of-the-art implementation of the AES-256 algorithm in GCM mode (authenticated encryption) with per-stream unique initialization vectors.

Not only this improves security by leaps, but (unlike v4 and v5) this method is applicable to all virtual file system types. Yes, with v6.x you’ll be able to apply AES-GCM encryption also to your S3, Azure, Google, and SFTP virtual file systems, not just the disk-based ones!

This gigantic step forward, though, comes with a small trade-off: version 6.x will no longer be able to access or support the old DiskAES256 encryption, so a method to decrypt your old DiskAES256 storage is needed, in order to move those folders and files over to the new v6.x high-security standard.

Upon release of Syncplify Server! v6.x we will therefore also release this tiny app to decrypt your old DiskAES256-encrypted folders, so that you can then migrate them over to the new and more secure server version.

We have finished testing this little app, and we’ll make it available for free to all users (including users of the free edition) of our previous Server! versions upon release of v6.x.


V6 VFSs include: Disk, S3, Azure, Google Cloud, SFTP (all with optional at-rest encryption)

Syncplify.me Server! versions 1 through 5 have always historically supported only 2 typed of Virtual File Systems (VFS):

  1. Disk (with optional at-rest encryption via DiskAES256)
  2. SFTP (encrypted over the network but not at-rest on the remote site)

When Syncplify Server! v6 is released, though, depending on the edition you use it will include the following Virtual File System (VFS) types:

  1. Disk (local drives and SSDs, and remote NAS, SAN, iSCSI, …)
  2. Amazon S3 (store data in your AWS S3 bucket)
  3. Microsoft Azure Blob Storage (store data in Azure Cloud)
  4. Google Cloud Storage (store data in Google Cloud Platform)
  5. SFTP (store data on another SFTP server, useful for SFTP-proxying)

And all of them will also feature encryption at-rest on whatever local or remote storage they point to.