On 2017-01-26 03:12, Ant wrote:
As you guys know, both Gecko based web browsers are the (lat/new)est stable versions which I told them. "Can't they be made to also support modern protocols?" is what they asked. So, I am asking you guys on how to resolve/fix this security connection issue.
There are a lot of pieces to the puzzle here. Each side supports various combinations of SSL/TLS versions, cipher suites, and so on - and in many cases the software allows the administrator/user to enable or disable parts of it. I may speak ten languages and you may speak twenty, but if we have no languages in common, we can't have a conversation. The same applies to SSL/TLS.
I'm glad to see that it got sorted out this time; it sounds like they made a configuration error when they were trying to improve security. If you run into this sort of thing in future and want some troubleshooting info, try these two steps:
1. Go to https://www.ssllabs.com/ssltest/index.html and have it test the site that's giving you problems
2. Go to https://www.ssllabs.com/ssltest/viewMyClient.html - this will tell you what parameters your browser supports
The first one includes simulation of various browsers to show whether that browser can connect to the site and, if so, what parameters would be used. It doesn't include Seamonkey but it does include a few Firefox versions so you may find your answer in there without even resorting to step 2. (I believe it simulates default settings only, so if you've fiddled with some of your settings, you may get a different result than the test does even if you're using exactly the same browser version.)
Failing that, comparing the list of what parameters the site supports from step 1 and what parameters your browser supports from step 2 will often show that there's a mismatch which prevents communications.
_______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
