Pulseway runs on .NET Framework 4.0 which only supports SSL 3.0 and TLS 1.0. We've disabled SSL 3.0 as it's insecure so there is only TLS 1.0 available now. There is a registry hack that enables Pulseway to use TLS 1.1 and TLS 1.2 on systems where there's .NET Framework 4.5 (or higher) installed and can be enabled by running the "Enable TLS 1.2 in .NET Framework 4.0" built-in automation script and restarting the Pulseway service.
We are planning on setting up a .NET Framework 4.5 release channel and automatically switch agents to that update channel if we can detect .NET Framework 4.5 (or higher) thus adding support for TLS 1.1 and TLS 1.2 out of the box. This change is scheduled to happen by the end of this year.
-Paul
Hi Paul,
good to hear that there is a "quick and dirty" fix for this issue.
But somehow i don't understand how to do this "running the "Enable TLS 1.2 in .NET Framework 4.0" built-in automation script".
Could you please let me know how i could enable this registry hack on an pc running client 5.1.2.
Support for TLS 1.2 on Agent for PCI 3.2 Compliance
in Feature Requests
Posted
Hi Paul,
good to hear that there is a "quick and dirty" fix for this issue.
But somehow i don't understand how to do this "running the "Enable TLS 1.2 in .NET Framework 4.0" built-in automation script".
Could you please let me know how i could enable this registry hack on an pc running client 5.1.2.
Thank you very much in advance.
sascha