OTFE (on-the-fly-encryption) with Syncplify.me MFT!

We’ve just added a MAJOR feature to Syncplify.me MFT! (not abailable in the Alpha-1 download yet, it’ll be in Alpha-2): OTFE, which is short for on-the-fly-encryption.

Basically, when OTFE is enabled, Syncplify.me MFT! encrypts files as they are uploaded to a remote file server (SFTP, FTP, S3, whatever, …) and decrypts them as they are downloaded back to the local machine.

This encryption/decryption happens on-the-fly, directly on the uploaded/downloaded data stream, so it doesn’t need to use temporary files on your disk; the entire process is very memory-friendly, because it encrypts/decrypts small buffers as they are transferred. Continue reading

How to: monitor local folders in mftJS and upload files as they appear in it

This article refers to the mftJS language, which is the special “flavor” of JavaScript designed by Syncplify for the upcoming Syncplify.me MFT! software product.

Let’s see the code first, then we’ll explain the details.

 

Continue reading

Two typical high-availability (HA) deployments

The most important improvement brought about by Syncplify.me Server! version 5.x is the simplicity with which you can create a true active-active high-availability (HA) set with it.

In fact, as of version 5.x, you don’t have to deploy a database replica-set anymore, which is hard to do and requires at least 5 virtual machines (2 for the SFTP nodes, and 3 for the database); Syncplify.me Server! version 5.x can achieve a totally fault-tolerant, active-active, highly-available deployment with just 2 virtual machines!

Continue reading

How to override permissions on subfolders inside the user’s Home VFS

Syncplify.me Server! version: 5.0.0+

As of version 5.0, Syncplify.me Server! allows to override permissions on sub-folders that are physically contained inside a user’s Home VFS.

Let’s say, for example, that the actual directory structure on disk is the one you see in the picture here below:

Clearly you will want to apply different permissions to the various sub-directories under that root, right? Continue reading

How to upgrade Syncplify.me Server! from V4 to V5

The video here below shows the recommended procedure to upgrade your Syncplify.me Server! from version 4.x to the new version 5.x.

This article assumes you’ve already read and understood the following 2 knowledge base articles, before you attempt the upgrade process:

It is recommended, before upgrading to v5.x, to make sure that you’re running the latest version 4, which is v4.2.5.

Also, it should go without saying (but we say it anyway), that prior to any major upgrade like this you should always make sure to take a snapshot or a full backup of the machine/VM running your existing version. This way, should anything go wrong during the upgrade, you can always go back to your old v4.x in no time.

Last but not least, the “magic URL” mentioned in the video, the one to backup your old v4.x configuration is:

 

Syncplify.me Server! v5: how to add a node/server to a high-availability (HA) set

This article embeds a video that shows how to add an additional node/server to an existing Syncplify.me Server! v5, turning it into a high-availability (HA) deployment.

This video only deals with the addition of the second node, we strongly recommend you to also check out this other article to learn how to deploy the first node.

How to install Syncplify.me Server! v5

This article embeds a video that shows how to install Syncplify.me Server! version 5.x either as a single standalone server or as the first node of a high availability deployment.

Now that you’ve set up your Syncplify.me Server! v5 as a standalone server, we suggest you check out this other article to learn how to add a second node and turn your SFTP server into a high-availability set.

ObjectName and VirtualObjectName deprecated in V5

Syncplify.me Server! version: 5.0.0+

Starting from version 5.0 of Syncplify.me Server! the ObjectName and VirtualObjectName variables (scripting engine and event-handling subsystem) will be deprecated.

They are still available, but they will be removed in future versions, so we do recommend to update all scripts that may be using such variables and make sure you use the new ones:

Session.ObjectName: substitutes ObjectName
Session.VirtualObjectName: substitutes VirtualObjectName

There are also two new similar values that will normally be empty, but may contain a string value only when responding to client commands like COPY, MOVE or RENAME. Such variables are:

Session.ObjectName2: contains the destination file name, relative to the local file system, for the object to be copied to, moved to, or renamed to (example: C:\SFTPData\NewFileName.txt)
Session.VirtualObjectName2: contains the destination file name, in POSIX-compliant format, for the object to be copied to, moved to, or renamed to (example: /SomeFolder/NewFileName.txt)

How to: SFTP authentication via one-time passwords (OTP)

Syncplify.me Server! version: 5.0.0+

Occasionally our customers ask if it’s possible to implement some form of one-time password (OTP) authentication for their SFTP users. Considering the complexity of the SSH authentication scheme, such task is definitely not trivial. To ease the process, Syncplify.me Server! V5 adds two new event-handlers and several functions to the scripting framework. This article explains how to use them to accomplish OTP authentication over SFTP. Continue reading

How to use VFS.ImportFile and VFS.ExportFile

Syncplify.me Server! version: 4.1.6+

As of version 4.1.6, Syncplify.me Server! added 2 new functions to the VFS object for you to use inside your event-handling scripts (requires the Ultimate edition of the software).

Say, for example, that you have an encrypted VFS, like a VFS of type DiskAES256 as shown in the picture here below: Continue reading