Since the recent demise of Scroogle, that I used exclusively for years, I have begun using Startpage.com HTTPS search engine exclusively. I have had GoDaddy disabled in Certificate Manager for years now on all browsers. I want my browsers to notify me each time a GoDaddy cert is used and then I decide on an individual basis for each site if I want to allow the cert one time or permanently or simply not visit that site. That works fairly well in Fx and SM (and works superbly in Opera, and fine also in Iron and IE).
When I try to do a search using StartPage HTTPS from the search bar, SeaMonkey throws an error message about the GoDaddy cert and does NOT provide me with the opportunity to tell it to accept the cert permanently. The message says "Secure Connection Failed" and my options are to "View Certificate" or "Cancel". Neither option is useful. I need the window that allows me to instruct SM to allow an exception either one time or permanently for StartPage.com HTTPS and for Amazon.com. On Fx, both ver 4.01 and 10 Enterprise, I get the correct window to add a security exception for StartPage. Fx, after many, many times of forgetting the command to remember the permanent exception, now finally seems to remember. If I click on the StartPage icon on the address bar, I am told that I have added a security exception for the site and the address bar is yellow. Because SM won't let me add an exception because I cannot reach the window where I can do that, I get what appears to be StartPage HTTPS search (because the address starts with HTTPS not HTTP) but is actually HTTP. That is misleading and not what I want. For Amazon, on BOTH SM and Fx, I get the window that SM is also giving me for StartPage so I cannot get to the window where I can make the permanent security exception. Amazon stupidly uses certs from two providers (Verisign and GoDaddy) and that is apparently confusing both SM and Fx since I have GoDaddy disabled and Verisign enabled. Again, Opera has no problems with this setup and neither do Iron or IE but I want to use SM and Fx. I am NOT willing to enable GoDaddy certs globally on Fx and SM and that should not be necessary for StartPage HTTPS and Amazon to work correctly. SM and Fx are supposed to allow the user to disable cert authorities and then make exceptions if needed. But this process is broken on SM for StartPage and Amazon and works only for StartPage (after much effort) on Fx. If I restart either browser and choose "resume last session" and any tabs were open to Amazon or StartPage HTTPS both browsers immediately start throwing errors about the GoDaddy cert and those tabs become unusable and the repeated errors about the certs slow down the loading of the other tabs. I also have all Comodo related certs disabled in all browsers (since Eddy Nigg was able to purchase a cert for Mozilla.com on Christmas eve 2008) and I have never found a site where I was not correctly presented with the window titled "Get Me out of Here!" where I then click repeatedly to get to the window where I can examine the cert and make an exception if I wish. It is puzzling that SM and Fx only seem to have problems with GoDaddy disabled certs and not with Comodo and Comodo related ones. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
