I get the same - on XP.
And I believe its going to be (
primarily) an XP issue.
In this case, I believe it going to be something like Salamander is relying on
OS features in order to negotiate the SSL connection, & XP does not have the built-in (cipher) support needed.
Now, suppose it is also possible that Salamander could supply the "bits" needed
outside of what the OS provides, in which case the connection would work... (But given that XP is EOL <well, kind of

>, including EOL to Salamander, its kind of a moot point.)
Similarly in my download manager, Net Transport, which at this point is old, many times I'm unable to connect to SSL sites - some, not all, suppose it depends on how the site is configured, & I'll get messages like:
URL:
https://github.com/avih/dejsonlz4/relea ... 4.v1.1.zip
Code: Select all
06/30/2017 11:28:39 AM.828 The supplied message is incomplete. The signature was not verified.
At those times, I'll just jump to WGET (or through my browser), which works.
Code: Select all
WGET.exe https://github.com/avih/dejsonlz4/releases/download/v1.1/dejsonlz4.v1.1.zip
This hints at TLS 1.2, which is an unknown entity to XP.
FIX: "The supplied message is incomplete" error when you use an FTPS client to upload a file in Windows
Support for SSL/TLS protocols on Windows
https://www.google.com/search?q=XP+The+ ... unofficial
XP, IE8 (cough), only talks about TLS 1.0.
