RSA, DSA and ECDSA host keys

Syncplify.me Server! version: 4.0.0+

Our users are aware that old Syncplify.me Server! versions (from 1.0 to 3.x) used to support only a single host key, and it had to be an RSA key.

As of version 4.0, though, Syncplify.me Server! supports RSA, DSA, and ECDSA host keys, and it support multiple (unlimited) host keys per virtual server.

The addition of DSA keys was mostly driven by the fact that some of our customers possess legacy DSA host/server keys that they are required to use, in order for certain client applications to work properly. The addition of ECDSA host keys instead is a truly remarkable new feature, and to understand why just check out the comparison table here below: Continue reading

Syncplify.me Server!: upgrading to version 4.x

Syncplify.me Server! version: 4.0.0+

Syncplify.me Server! v4 is more than just a major release. The software was totally redesigned and nearly entirely rewritten. The back-end database is new, both in structure (JSON) and with regards to the engine (MongoDB). The virtual file system (VFS) implements a true separation of the file transfer engine and the storage. Management is now entirely based on a rich set of REST API, to which we provide 2 front-ends: a modern Boorstrap/AngularJS secure web interface, and a completely redesigned CLI (command-line interface). For all these reasons, in order to upgrade to version 4 and keep your configuration and user database, you will have to carefully follow the procedures explained in this article, and especially in the VIDEO here below. Continue reading

Can I run Syncplify.me Server!’s HTTP REST API on port 443?

Syncplify.me Server! version: 4.0.0+

During the installation process of Syncplify.me Server! v4.x (or greater) you will be asked the IP address and port to which the new HTTP REST API service should bind. While in most cases 0.0.0.0 (all interfaces) is a safe choice for the IP address, it is important to carefully choose a port.

In order to help you choose, we have prepared a very easy diagram. Just answer the questions on the diagram, and you’ll know which port (not) to use.

HTTPS Port Choice

This said, in order to limit automatic probes (bots), choosing a non-standard port is probably always the safest way to go.

Syncplify.me Server! v4: simplicity and power

Syncplify.me Server! version: 4.0.0+

Designing software for a large customer base is not an easy task. Some users want simplicity, very few and easy “clicks” to get their server up and running, no distractions, not too many things to look at, and that often sacrifices power. Other users (usually Enterprise customers) need to be able to perform complex deployments, integrated into complicated existing environments, they need to be able to configure every single tiny detail of the solution to fit into a much bigger architecture, and all that power often sacrifices simplicity.

When we designed Syncplify.me Server! v4 we have kept all of this in mind, and we have accomplished a design that “adapts” to the user’s needs and desires. In fact, v4 features simplified, wizard-driven configuration for those users who require simplicity, and yet advanced users can plan and execute their deployments down to the tiniest detail by configuring every single aspect, even when the architecture is very complicated. Continue reading

Syncplify.me Server! v4: the all-new VFS

Syncplify.me Server! version: 4.0.0+

One of the biggest changes that version 4 will bring to Syncplify.me Server!’s user base is the all-new Virtual File System. This is such an epic change that it’s actually one of the reasons why the release of v4 is taking longer than expected… but it will be worth the wait.

Check out the following comparison table to appreciate the main advantages of the new VFS over the previous approach (that was based on “virtual directories”):

Virtual Directory Approach (v1, v2, v3)Virtual File System (v4)
Virtual directories can only be placed directly under the user's home directoryIn a VFS, virtual folders can be placed anywhere, even nested within each other
All virtual directories are accessed "as" the user who logged in (single impersonation)In a VFS, each virtual folder can accessed "as" a different user profile (multiple impersonation)
Virtual directories mapped to UNC paths could not be accessed by "normal" user profiles, only by Windows or AD user profilesEach virtual folder has its own impersonation criteria, so even "normal" user profiles can access virtual folders mapped to remote UNC paths

Continue reading

Maintenance release: Syncplify.me Server! v3.1.21.61

We have just released version 3.1.21.61 of our Syncplify.me Server!

This new maintenance release fixes a bug in the Configuration Manager that prevented the hash code of some CA-issued certifricates (especially wildcard ones) from being calculated. This was just a visualization bug, all certificates were still working correctly in the SFTP/FTP(S) server, but if you use a CA-issued wildcard certificate you might want to install this update.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.20.60

We have just released version 3.1.20.60 of our Syncplify.me Server!

This new maintenance release fixes a bug in the AppendStringToFile function of the event-handling scripting framework. This update is not necessary if you aren’t running scripts containing the above mentioned function.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.19.59

We have just released version 3.1.19.59 of our Syncplify.me Server!

This new maintenance release fixes a bug in the AVBL command that was affecting the FTP protocol family only (SFTP was not affected). Thanks to Martin for identifying and reporting this issue.

As usual you can download the latest version from our web site. Thank you!

Syncplify.me Server! v4: manageable via JSON REST web service

Syncplify.me Server! version: 4.0.0+

Getting closer and closer to the early availability of Syncplify.me Server! v4, we think it’s time to share with our customers one of the biggest new features they can expect to find in the upcoming major version: a secure (authenticated) JSON REST web service that allows granular management and configuration of the server, user database, blacklist, and every other aspect.

Continue reading

Maintenance release: Syncplify.me Server! v3.1.17.57

We have just released version 3.1.17.57 of our Syncplify.me Server!

This new maintenance release fixes a bug in the global speed limit configuration. Under certain circumstances, in fact, only user-specific speed limits were enforced, while global speed limits were ignored; now it’s fixed.

As usual you can download the latest version from our web site. Thank you!