Op zondag 27 augustus 2017 06:42:59 UTC+2 schreef David E. Ross: > On 8/26/2017 9:17 PM, David Guymer wrote: > > David Guymer wrote: > >> David E. Ross wrote: > >>> On 8/26/2017 12:34 AM, David Guymer wrote: > >>>> There is something wrong with SeaMonkey 2.48.Every page I go to I get a > >>>> certificate warning. > >>>> > >>>> I have aspersky Total Security 18.0. I have imported the Certificate > >>>> from this program with the same warning afterwards. > >>>> > >>>> All other browswers are unaffected. News and mail are unaffected in > >>>> SeaMonkey. > >>>> > >>>> David Guymer > >>>> > >>> > >>> Give us a link to an affected Web page, a page that does not require a > >>> login to an account that I do not have. > >>> > >> > >> https://www.foxtel.com.au/my-account > > > > Another important site that won't load is > > https://my.gov.au/LoginServices/main/login?execution=e1s1 > > > > David Guymer > > > > Windows 7 > SeaMonkey 2.48 > > That one loaded okay. The site certificate for www.my.gov.au is owned > by the Australian Department of Human Services. It and the intermediate > certificate were properly installed on the www.my.gov.au server. Both > successfully chained to the DigiCert High Assurance EV Root CA > certificate, which was installed on my PC with SeaMonkey. > > It is possible that your file of root certificates has become corrupted. > To restore it, I suggest the following: > > 1. On the SeaMonkey menu bar, select [Help > Troubleshooting > Information]. > > 2. Under "Application Basics", select the Open Folder button to the > right of Profile Folder. > > 3. Terminate all instances of SeaMonkey. > > 4. In the profile folder opened in #2, locate the file cert8.db and > delete it. > > 5. Relaunch SeaMonkey (which re-creates cert8.db) and try your problem > Web sites again. > > If you truly trust the Australian government's Web sites (why not?), you > might also try disabling Kaspersky just before attempting to access > those sites. Remember to enable Kaspersky afterwards. > > -- > David E. Ross > <http://www.rossde.com/>
I use 2.49.3 and Bullguard, and I have the EXAT same issues as descrbed by OP, so I tried these steps (locate the file cert8.db and delete it, reboot SM), same issues persists.... IS THERE A SOLUTION OR NOT?? _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
