Syncplify Server! v6.2.26 released

Importance of this update: [HIGH]
What’s changed?
  • Upgraded the compiler to the latest version, which comes with many fixes in the compiler’s standard library
  • Huge improvement in Protector(TM) performance, strikes are now counted up to 1000x faster than before
  • Added STSPreload to the global configuration in the SuperAdmin UI
  • Slightly relaxed RSA key security requirements to restore functionality of PKI authentication using old and insecure RSA keys (only when already known to the server prior to the changes made to prevent Terrapin)
  • Upgraded back-end SyngoDB database server to v4.11.0

IMPORTANT NOTE: those who are running the “worker” system service under a different account (not System or LocalSystem) will need to re-configure the service to run under such account after upgrading from any version number <= 6.1.12)

Upgrading from v6.x.y is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!


Syncplify Server! v6.0.12 released

Today we released Syncplify Server! v6.0.12; here’s what’s new and improved in this version.

Importance of this update: IMPORTANT
Fixed
  • Internal refresh timeout for the Dashboard (Admin UI) has been fine-tuned
  • TLS config for FTP(E/S) now works as expected when it is set as “Disabled”
  • Sharing objects via WebClient! is now subject to the correct set of permissions
  • Fixed bug in enforcement of Protector’s behavior that could lead to wrongful block-listing of legitimate client IP addresses

Upgrading from v6.0.x is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!


More than 100,000 attacks on V6. Zero hacks.

This is mostly an update to a previous post we published some time ago.

Our honeypot Syncplify Server! V6 has been up for about a month now, while we work hard on developing the management UIs, and it has received more than 100K attacks thus far: 114,671 at the time this post is being written, to be precise.

The good (very good, actually) news is that none of those attacks has yielded any result to the attackers. Nothing. Nichts. Nada.

They tried.

They failed.

Syncplify Server! V6 wins. 🙂


Testing the blocklist cache

Every Syncplify Server! operator is familiar with Syncplify’s ProtectorTM technology, which prevents attacks and hacking attempts, and automatically puts the attacker’s IP address in the blocklist (formerly known as “blacklist”).

But in every Syncplify Server! version prior to v6, checking whether or not an incoming request is coming from a blocked IP address implied a query to the database, which can take a millisecond or two. In v6, though, we have now implemented an in-memory cache with automatic TTL, which effectively reduces the number of such DB queries by up to 90%, and the time taken from milliseconds to just a few microseconds (yes, it’s up to 1,000 times faster than querying the DB).

Here’s a blocklist usage and cache-hit report for the past 2 days of operation of our honeypot:

{
     "rejectedConns": 2331,
     "addedToBl": 2262,
     "hitsOnBl": 2250,
     "hitsOnBlCache": 1985
}

Out of 2250 blocklist hits, 1985 (88.22%) were gracefully handled by the in-memory cache.