Maintenance release: Syncplify.me Server! v3.1.16.56

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

This new maintenance release fixes a bug in the FileToString function that was erroneously assuming the file encoding was always UTF. Now the file encoding is properly detected before the “read” operation takes place.

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

Syncplify.me Server! v4: from Blacklist to Protector!

One of the most popular and widely appreciated features of Syncplify.me Server! has always been its powerful and automatic blacklist. The upcoming Synplify.me Server! v4 is going to bring that concept to an even higher level with its Syncplify.me Protector!™ technology.

Protector! is a leap forward versus the blacklist as our users know it. It’s still fully automatic, but its controls are now 10 times more accurate and integrated much deeper in the protocols themselves. If used to its full potential, Protector! can be very harsh, therefore we felt the need to let our users configure its “sensitivity”. It is possible to set Protector! to either one of the following 4 “aggressiveness thresholds”: Continue reading

Firewalls and FTP external IP address for PASV

Yesterday we came across what, at first, seemed to be a pretty odd case, and we think it’s worth sharing it with our users.

Most firewalls (we’d say all the ones we know) have NAT/PAT capabilities, and many are able to perform protocol-level inspection when the connection is not encrypted. SSH (and SFTP) are always encrypted, but FTP can be either encrypted or not; yet, theoretically protocol inspection should only prevent protocol-related attacks, not modify client requests or server responses.

Yet, yesterday a customer with a perfectly configured instance of Syncplify.me Server! was experiencing a weird behavior: FTPS/FTPES (encrypted) sessions were working perfectly, while plain FTP sessions were dropped upon every attempt to open a data connection to transfer files. Continue reading

Maintenance release: Syncplify.me Server! v3.1.15.55

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

This new minor update (maintenance release) fixes a bug that affected only Windows Server 2012 and 2012R2 and prevented Syncplify.me Server! from correctly identifying overridden home folders for network user.

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

SFTP Server on Windows 10

This article refers to Syncplify.me Server! v4.0, which – at the time the article is being written – is still in beta, and is not yet available for purchase by customers. The purpose of this article is to inform our users about some important upcoming features.

In an effort to be always few steps ahead of the competition, we are making sure the upcoming Syncplify.me Server! v4 plays well with the new version of Microsoft’s operating system. So when you have to choose your next SFTP server for Windows 10, you know where to go. Continue reading

Extending your SFTP Server: Lesson #1

This is the first of a series of video lessons to help our users learn how to unleash the full power of Syncplify.me Server! by writing scripts that are executed automatically upon occurrence of certain events.

This first script is kind of a “hello world”, but it’s meant to give our users a glimpse of the features Syncplify.me Server! puts at their disposal.

Once you’ve watched the video, if you don’t want to re-type the script by hand, here’s the source code for you, ready to copy and paste.

 

Syncplify.me Server! v4: high speed and savvy RAM usage

This article refers to Syncplify.me Server! v4.0, which – at the time the article is being written – is still in beta, and is not yet available for purchase by customers. The purpose of this article is to inform our users about some important upcoming features.

The development team is running some final tests on the core engine of the upcoming Syncplify.me Server! v4, and we’re witnessing amazing results.

Long story short, the brand new core engine of version 4.0 is not only much (much!!) faster than any previous version, but it uses on average half of the RAM! See the following screenshot of the Task Manager taken from one of our test systems: Continue reading

Maintenance release: Syncplify.me Server! v3.1.14.54

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

This new minor update (maintenance release) fixes a tiny bug that caused the psftp client to raise an error condition upon issuing a bye/quit command. Now the session termination with that particular client program is handled correctly.

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

Maintenance release: Syncplify.me Server! v3.1.12.52

We have just released Syncplify.me Server! v3.1.12.52, a maintenance release that comes with the following improvements and new features:

  • User profile automatic expiration date can now be set via CLI (command-line interface)
  • A tiny memory leak in the logging subsystem has been fixed
  • Send buffer performance improved in critically slow network conditions

In order to set the expiration date using the CLI, you have to pass the date to the -autoexp parameter in RFC959 format (YYYYMMDDHHmmSS, no spaces). Here’s an example that will set the expiation date for a user at noon on Christmas day 2015:

Passing any parameter in a format other than the RFC959 date format specified here above, will disable the automatic expiration of the user profile. The following commands all disable the automatic expiration:

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

Maintenance release: Syncplify.me Server! v3.1.11.51

We have just released a maintenance update of our Syncplify.me Server! software. This new version features the following improvements:

  • Fixed a bug in the “FileCopy” function in the event-handling subsystem (scripting framework)
  • Fixed a potential memory leak in the SMLogServer.exe logging system service

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