ClassicHasClass wrote:Right, but is that because SSL3 got turned off, or because the library isn't loading? It may not be possible to tell from the client.
However, I *think* that version should have TLS 1.0 capability.
I'm not sure from the client, because of these two messages:
Could not initialize the browser's security component. The most likely cause is problems with files in your browser's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the browser and fix the problem. If you continue to use this browser session, you might see incorrect browser behaviour when accessing security features.
SeaMonkey can't connect securely to ssl.gstatic.com because the SSL protocol has been disabled.
TLS and SSL3 are set to enabled.
I've installed SSL1 on the system, also as a heads up to everyone with a hobbyist license: There are a LOT of patches missing from the HPE site, and the psci patch is outdated (should be V0400) and will prevent you from installing the V1000 update that. I've let the HPE people know about this but if they don't get around to it or you don't have the current password to the FTP, you can get what you need here: http://mirrors.pdp-11.ru/_alpha/_VMS/Op ... 4_Updates/
SSL1 requires VMS84A_PCSI-V0400 and VMS84A_UPDATE-V1000, the first can only be found at that link for the time being and the other is on the HPE FTP, but can't be installed without the pcsi update. You'd think they'd check that...