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

Syncplify.me Server! v3.0: improved command-line interface (CLI)

Besides a totally new graphical Configuration Manager that will allow local and remote configuration (over any Internet connection) of your Syncplify.me Server!, the new v3.0 will also feature a greatly improved command-line interface (CLI) tool.

Being intended as an integration instrument, the CLI doesn’t have remote configuration capabilities, but it has some interesting features such as some new “visualization” capabilities like – for example – the ability to show the current contents of the blacklist (and alter it):

cmdblist

Once again thanks to our dev-team, our beta-testers, our investors, and all the people who are making this possible.

Syncplify.me Server! v3.0: improved session object

Thanks to our precious beta-testers (Izzy, Antonio, and “the gang”) we have been greatly improving our session object, for the joy of all users who take advantage of Syncplify.me Server!’s event-handling subsystem in order to run their own scripts.

In addition to all the properties and methods that were already present in v2.x, the new version will also feature the following ones:

Continue reading

Syncplify.me Server! v3.0: more on speed limits…

As we already mentioned in a previous post, Syncplify.me Server! v3.0 will feature a very granular configuration regarding speed limits. This post explains how such limits work in detail.

First of all the are 2 lists of limits: a global list that refers to the whole server (regardless of the user who is connecting) and a second list that is defined in the user profile, and only affects that specific user.

Second, and most important, it is essential to understand that the speed limit list defined on a specific user, always prevails over the global one.

So let’s assume, for example, that the following limits are defined globally:

And the following limits are defined specifically for the user johndoe:

When the user johndoe connects from the local area network (192.168.X.X) he will have an upload/download speed limit of 1024 KB/s, as set in his own profile, regardless of what the global configuration limit is for the same network; the user configuration always supersedes the server’s global/default configuration.

Syncplify.me Server! v2.0.7.27 hot-fix 1

If you have downloaded and installed Syncplify.me Server! v2.0.7.27 in the past 6 days, and are experiencing problems with the X.509 certificate on your FTPS (or FTPES) connections, please download v2.0.7.27-hotfix-1 from our web site, and update your instance.

This is a pure hot-fix release, nothing else has been changed, no improvements were made, and no features were altered. Therefore, if you are not experiencing any trouble, you won’t need this update. Thank you.

Syncplify.me Server! v3.0 will feature speed limits

Just a quick note to let our users know that our dev-team has just finished implementing speed limits in Syncplify.me Server! v3.0. Tested. It runs smoothly.

Speed limits can be configured globally (server-wide, per instance) as well as individually for each user, and the upload and download speed limits can be specified separately.

Here you can see a file transfer with the speed limit disabled. This test was performed on a 100 Mbps LAN, and as you can see the upload speed is 12.95 MB/s (103.6 Mbps, with compression, LAN bandwidth is saturated).

Image2

Now, this is the same test, but with speed limit enabled. As you can see, the upload only takes up to the allocated bandwidth and does not saturate the LAN.

Image1

Speed limits can be configured globally, per user, or per network. Therefore you can have different speed limits applied to the same user depending on the IP address he/she is connecting from.

New release: Syncplify.me Notepad! PORTABLE EDITION

We received many requests from our users for a portable version of Syncplify.me Notepad! A single self-contained EXE that one can simply put on a USB stick and carry around without the need to install it on the target computer.

We did it!

Feel free to download Syncplify.me Notepad! Portable from our web site, as usual. Thank you.

New release: Syncplify.me Server! v2.0.7.27

After the recent addition of the public IP to be used for PASV connections, we have now improved such feature by adding the possibility to specify a “local LAN” address space to which the above mentioned configuration will not be applied. Basically this makes your NATted server able to accept PASV connections both from inside and outside your Local Area Network (LAN).

You can download the latest version from our web site, as usual.