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

Syncplify.me Server! v4.1.7 released

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

  • Fixed: bug in the SSH “Shell” subsystem that prevented the user to be placed in the correct home directory upon opening a shell
  • Fixed: bug that prevented the TLS socket closure notification packet from being sent (only on Active FTPS data connections, no other protocol was affected)

Warning: upgrading to this version from any version prior to 4.0.34 will invalidate your license, so please if you are a customer – before you upgrade – contact us to request a license reset.

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.

Syncplify.me Server! v4.0.10 released

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

  • Improved download speed by adding automatic self-adjustment of TCP window size
  • Improved analytics support
  • Improved support for AWS cloud platform

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

SSH Server Key: best practices

Upon installation, Syncplify.me Server! auto-generates a 1024 bit SSH Server Key, and that is enough for most users and most scenarios.

But some of our users may have higher needs in terms of bit-length (2048 or even 4096) or may need to use a specific SSH Server Key provided by a third party. This article covers such scenarios.

If you only need a higher bit-length, the easiest way is to generate a new SSH Server Key from within the Configuration Manager. In order to do so, simply click the “gear” button next to the SSH Server Key field, as shown in the picture below: Continue reading

SSH Server Key ≠ FTPS (SSL/TLS) Server Certificate

From time to time our users ask how to use their X.509 (SSL/TLS) certificate for SFTP.

The one-line answer is: it’s not possible. But let’s dig into the topic and explain why, and above all how to implement server certificate and keys correctly.

First of all it is important to identify which protocol we intend to use, and what are its peculiarities: Continue reading

SSH Server: we need your opinion…

As of today, by design, Syncplify.me Server! doesn’t send back “echo” characters when the user connects over SSH and opens a Shell. This allows us to perform some additional checks on protocol violations that would be harder (although not impossible) to perform if “echo” was active. Yet, few of our customers have requested “echo” to be enabled. What so you think about it?

[yop_poll id=”1″]