Syncplify.me Server! v4.0.33 released

We have just released version 4.0.33 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: behavior of [%USERNAME%] parameter in VFS when using Active Directory group authentication

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Using the DiskAES256 encrypted VFS

Syncplify.me Server! version: 4.0.0+

As of version 4.0, Syncplify.me Server! has introduced storage access via VFS (Virtual File System). This new storage virtualization layer allows an administrator to choose among different ways to access the underlying file system; one of them, that encrypts/decrypts data at-rest on the fly, is the DiskAES256 VFS.

When a VFS is of DiskAES256 type, all files uploaded to that VFS will be encrypted and then saved to disk. Similarly, when an SFTP client downloads them, the files will be read from disk and decrypted on-the-fly before they are sent to the client over the network (don’t worry SSH/SFTP network encryption still applies).

So, because of the way it works, as described here above, when you create a new VFS of type DiskAES256 you have to make sure it points to an empty path/directory (that has no files in it). Otherwise it would try to decrypt existing files that are not encrypted in the first place, and fail. Continue reading

Syncplify.me Server! v4.0.13 released

We have just released version 4.0.13 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed a bug in the DiskAES256 encrypted Virtual File System (VFS) – this bug prevented files from being correctly downloaded if the client requested odd-sized or unaligned buffers

Very important: to fix this bug we had to change the way we encrypt files at-rest via DiskAES256 VFS; so if you use this particular type of VFS, please, make sure you download all your files to a non-encrypted location before you update to 4.0.13, after the update please delete all files from the location that was protected by the DiskAES256 VFS and re-upload them all. We sincerely apologize for the hassle.

As usual you can download this new release from our website.