Why did my license revert back to FREE?

Occasionally we receive emails from customers whose paid license has reverted back to “free” or “freeware” mode, and they ask us why that happened.

To reduce the phenomenon of software piracy, Syncplify.me Server! binds its licenses to a so-called System-ID upon their activation. This means that, once a license has been activated, it is bound to that System-ID forever, unless we reset it (thus allowing activation on a new machine or VM).

You can find your System-ID in the License page of the SuperAdmin web interface:

Continue reading

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: fix a white-list or safe-list suddenly empty

Syncplify.me Server! version: 4.0.0-4.1.4

Occasionally users report that their white-list or safe-list in the web management interface suddenly shows up as “empty” and they cannot add any more IP addresses or networks to it. That bug was already previously documented in our knowledge base, and has been resolved/fixed as of version 4.1.5.

The misbehavior is caused by the fact that an Admin has added the same IP or network twice to the list(s).
Upgrading to the latest version will prevent Admins from adding any more duplicates… but it does not sanitize the existing lists, so you will still have to “clean” your lists manually before you can see them again. 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

Configuring SSL/TLS security for the Web/REST Service

While SSL/TLS security configuration for the FTPS protocol is entirely self-contained, Syncplify.me Server!’s Web/REST service relies on Windows’ HTTP.SYS subsystem, which is the same subsystem IIS is based on, and therefore its security configuration has to be made at operating system level.

In order to ease the process we recommend Natarc’s IISCrypto, a free and powerful utility that helps achieving the task with just a few mouse clicks. Continue reading

How to: use a CA-issued certificate (the long way)

Syncplify.me Server! version: 4.0.0+

If you already own an X.509 (SSL/TLS) digital certificate in PFX format, you know how simple it is to import it into your Syncplify.me Server! and use it.

But many of our customers asked for a tutorial on the longer procedure of requesting a digital certificate to a certification authority (CA) via a certificate signing request (CSR). So here’s the fully documented procedure for you.

First of all you have to generate the CSR, and to do that you will simply go to the Security->FTP(E/S) menu and select the option in the picture below from the certificate drop-down menu: Continue reading

Ensuring Syncplify’s MongoDB instance safety

Syncplify.me Server! version: 4.0.0+

In light of the recent news regarding ransomware targeting MongoDB, we would like to inform all of our users and customers that we are actively working to add support for MongoDB’s authentication directly inside our software.

In the meantime, though, it is very important to understand that:

  • set aside the hype, a good network security model already addresses 99% of all the issues of this type (DB-connectivity related)
  • Syncplify’s specific MongoDB instance uses port 28038 (instead of the standard 27017) and is therefore not targeted by the above mentioned ransomware
  • Syncplify’s specific MondoDB instance only accepts requests from localhost (127.0.0.1) unless you have explicitly created a Windows Firewall rule

Because of the above reasons we believe that all Syncplify.me Server! instances deployed in non-HA mode are safe unless the network and Windows Firewall configuration has been altered by the users/customers themselves.

For HA (high-availability) instances, we do strongly recommend our users/customers to make sure their network firewall and Windows Firewall rules only allow connections to the DB server(s) from the machines running the SFTP front-end nodes. No other machine should be allowed to connect to your DB server(s).

This said, we want to reassure everyone – once again – that we are also actively working (with high priority) to add MongoDB authentication directly into our software.