Syncplify.me MFT! Beta-1 is available

Syncplify.me MFT! has just reached “beta.1” stage. This is a major milestone for us, because all alpha versions only supported the SFTP protocol (useful to crystallize the functionalities) but this is the first version that also adds support for AWS S3, Azure Blob Storage, and Google Cloud Storage.

The “beauty” of MFT! stems from the fact that you can basically utilize the exact same script logic independently of the storage platform. Literally the only difference is the connection properties to the back-end platform, because that’s – obviously – dependent on which storage you use.

But since an example is worth more than a thousand words… here’s a simple script that lists a directory and uploads some files to S3:

Continue reading

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