On 08/31/2011 03:07 PM, Justin Wood (Callek) wrote: > On 8/31/2011 5:39 PM, NoOp wrote: ... >> Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But >> *worse* is that they reenstate DigiNotar Root CA. Tested both ways: >> >> 1. 32bit linux deleted DigiNotar Root CA and then did the update via >> Help|Check for Updates. DigiNotar Root CA is now back. >> Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 >> Firefox/6.0.1 SeaMonkey/2.3.1 >> >> 2. 64bit linux deleted DigiNotar Root CA and then did the update via >> Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded >> the entire bz2, deleted the old, and extracted to a new folder; >> DigiNotar Root CA is now back on that version as well. >> Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) >> Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 >> >> I've not tested any windows versions (yet). > > The root CA will still appear in the cert list, but it is blocked, > please test with a website.
Further to my other posts following this: If I delete the Root CA cert via: Edit|Preferences|Privacy & Security|Certificates|Manage Certificates|Authorities|click on 'DigiNotrar Root CA' and click 'Delete or Distrust' & 'OK'. The cert disappears. But the reappears when SeaMonkey is restarted (at least in several instances that I've tested). Why is that? Shouldn't the above _totally_ clear the cert from the database? > But its a factor of how this code works. > Not really IMO. See my questions above. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
