On 11/20/2014 07:01 AM, Paul Marwick wrote: > NoOp wrote: >> On 11/18/2014 01:50 PM, Paul Marwick wrote: >>> I've just hit a new problem with Seamonkey 2.30. >>> >>> Just finished installing a new small Linux server. I needed to access >>> the web page on the server. Fired up Seamonkey, entered https:<IP> and >>> the port number. And got this message: >>> >>> "An error occurred during a connection to test1:10000. The key does not >>> support the requested operation. (Error code: sec_error_invalid_key) >>> >>> The page you are trying to view cannot be shown because the authenticity >>> of the received data could not be verified. >>> >>> Please contact the web site owners to inform them of this problem." >>> >>> And it won't let me log on. Wonderful.... I know the key is not offical. >>> And I don't care - its on my internal network. At least in older >>> versions I was given a warning and allowed to make an exception. Seems >>> that I'm now to be "protected", even when I do know exactly what I'm doing! >>> >>> Firefox exhibits exactly the same over protective nonsense. In the end, >>> I had to use Chromium to access the setup page. >>> >>> Is this expected behaviour, or is it something I've (yet again) got >>> messed up in my profile? >>> >>> I've used Seamonkey since the old Mozilla suite. But if this is about to >>> become standard, it is about to get dropped. Permanently! >>> >>> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 >>> Firefox/33.0 SeaMonkey/2.30 >>> >>> Paul. >>> >> >> These might be of interest: >> >> <https://bugzilla.mozilla.org/show_bug.cgi?id=1084606> >> (Allow overrides for MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE (some cases >> of SEC_ERROR_INVALID_KEY in Fx33)) >> <https://stackoverflow.com/questions/26389964/firefox-33-0-wont-open-a-specific-local-application-error-code-sec-error-inva/26520093#26520093> >> <https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33> > > Thanks. That last link allowed me to fix it. I've got a number of small > servers out there that use Webmin, which was the main problem.
Excellent! > Generating a new key from within Webmin has fixed those that I can reach > - I'll have to go onsite for the rest, but it does work. You might try elinks & see if that will work. Also see: <https://bugs.launchpad.net/ubuntu/+source/elinks/+bug/769354> (elinks accepts self-signed ssl certificates without warning) may work in your favor :-) > >> >> You still should be able to set an exception via >> Edit|Preferences|Privacy&Security|Certificates|Manage Certificates >> >> > > I may have to try that if I find any sites in the wild that have the > same problem. > > Paul. > _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
