CrazyCanuck
Occasional Visitor
My VPN provider uses RSA 1024 and also uses sha1.
"The bad news doesn’t end there: 74% of certificates have an insecure SHA-1 signature, despite the fact that the majority of web browsers plan to depreciate and stop accepting SHA-1 signed certificates, as the algorithm’s weaknesses can potentially allow an SSL certificate to be forged, impersonating a server and intercepting critical data.
About 41% of SSL VPNs use insecure 1024 key length for their RSA certificates, which are used for authentication and encryption key exchange. RSA key length below 2048 is considered insecure, allowing various attacks.
10% of SSL VPN servers that rely on OpenSSL are still vulnerable to Heartbleed. And, only 3% are compliant with PCI DSS requirements, and none is compliant with NIST guidelines, which are considered a minimum required level of security."
http://www.infosecurity-magazine.com/news/most-ssl-vpns-are-wildly-insecure/
"The bad news doesn’t end there: 74% of certificates have an insecure SHA-1 signature, despite the fact that the majority of web browsers plan to depreciate and stop accepting SHA-1 signed certificates, as the algorithm’s weaknesses can potentially allow an SSL certificate to be forged, impersonating a server and intercepting critical data.
About 41% of SSL VPNs use insecure 1024 key length for their RSA certificates, which are used for authentication and encryption key exchange. RSA key length below 2048 is considered insecure, allowing various attacks.
10% of SSL VPN servers that rely on OpenSSL are still vulnerable to Heartbleed. And, only 3% are compliant with PCI DSS requirements, and none is compliant with NIST guidelines, which are considered a minimum required level of security."
http://www.infosecurity-magazine.com/news/most-ssl-vpns-are-wildly-insecure/