Fernando Rodriguez <frodriguez.develo...@outlook.com> writes: > On Thursday, September 03, 2015 9:53:39 PM lee wrote: >> Hi, >> >> since quite a while, seamonkey and its relatives are completely broken >> when it comes to use self-signed certificates. They just refuse the >> connection to the server, blocking you from accessing your email. >> >> Is there still no solution for this problem? I'm totally fed up with it >> by now. At work, I have frozen seamonkey at version 2.31 and >> thunderbird at some outdated version that still works with the >> certificates. Googling for a solution doesn't reveal one, either. >> >> Now I need seamonkey to access the email, and I can't very well turn it >> back to an outdated version just for that. >> >> BTW, if this won't be fixed, what are the replacements? > > This[1] is for firefox but should work similarly. Scroll all the way down to > "bypassing the warning". There's also an about:config option, I *think* it's > this one[2].
Thank you. The problem is that it doesn't let me add an exception. Only the older versions do that. All options to add an exception are disabled. There is 'browser.ssl_override_behavior', the value of which is 2. Guessing by what that means from [2], that should allow me to add an exception. 'browser.xul.error_pages.enabled' is enabled. There's also 'browser.xul.error_pages.expert_bad_cert', which is disabled. Let's see what that does ... still cannot add an exception when I enable it. [3] would indicate that it's advisable to set it to "true". Restarting seamonkey after changing it doesn't help. There's nothing wrong with the certificate, either. Older version work just fine with it. Mutt works fine with it. Gnus works fine with it. Evolution works fine with it. All of those are more recent than seamonkey 2.31. I could resort to unencrypted connections on the LAN to be able to upgrade the browsers and MUAs --- for security reasons, ironically --- but some ppl with laptops need to be able to connect from anywhere over the internet. So omit all security and use VPN for those to make things more secure by not using self-signed certificates but insecure connections? [3]: http://kb.mozillazine.org/Browser.xul.error_pages.expert_bad_cert > > [1] https://support.mozilla.org/en-US/kb/connection-untrusted-error-message > [2] http://kb.mozillazine.org/Browser.ssl_override_behavior -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
