We have just released SilverSHielD version 6.1.12.142.
This new version features only one small change: it adds one log line in case of failed authentication to help trace the origin (IP address) of the offender.
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact InSync Microproducts before applying this update/upgrade. Thank you.
We have just released SilverSHielD version 6.1.11.141.
This new version features only one small change: it ensures that all directories and virtual directories have the “permissions” bits properly set in the “attributes” extension (SFTPv4+).
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact InSync Microproducts before applying this update/upgrade. Thank you.
We have just released SilverSHielD version 6.1.10.140.
This new version improves the logging subsystem by adding an easy way to associate usernames with the IP addresses from which their connections are originated.
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact Extenua before applying this update/upgrade. Thank you.
We have just released SilverSHielD version 6.1.9.139.
This new version resolves an issue with white-list defined at user level, that in certain particular situations may have been skipped in previous versions.
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact Extenua before applying this update/upgrade. Thank you.
We have just released SilverSHielD version 6.1.7.137.
This new version features a greatly improved CLI (command-line interface) and several stability-related fixes to cope better with parallel password-harvesting attacks.
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact Extenua before applying this update/upgrade. Thank you.
We have just released SilverSHielD version 6.1.8.138.
This new version resolves an issue with the Management Console, where the PKI and Virtual Folders tabs would become read-only for certain user profiles.
Warning: if you’re upgrading from a version prior to 6.1.5.135, installing this new version may lead to loss/invalidation of your license. So if you are a licensed customer, please, contact Extenua before applying this update/upgrade. Thank you.
If you’re still running an old version of SilverSHielD (older than 5.5) please always contact Extenua before performing the update/upgrade.
In fact, the v6.x installer is guaranteed to automatically import your configuration, settings, and users when upgrading from v5.5, but may not be able to import from older formats.
An upgrade from version 4 or early 5 can be performed via an intermediate upgrade to version 5.5. Upgrade from older versions (developed by K2SXS before the acquisition by Extenua) may not be possible. So, please, contact us if you’re facing these scenarios.
Upgrading from v5.5 or older to the latest version 6.x, instead, is totally automatic and can be performed right away, no need to contact us in this case.
If you have upgraded SilverSHielD from an old version (5.x or earlier) to the latest version you may see a “SQLite3 Error 8” message when attempting to save the configuration through the management console, or to apply a new license code.
SilverSHielD provides two alternative methods for license activation behind a corporate firewall/proxy, or when the server is totally offline (private LAN with no Internet access).
If the Internet is accessible through a proxy, there is a specific configuration panel in the Management Console, as shown in the image below.
It is very important to understand how the max number of concurrent clients and the max number of concurrent connections per client settings work.