"David E. Ross" <[email protected]> wrote in message 
news:[email protected]...
> On 9/17/12 1:08 AM, Desiree wrote:
>> I have had all Comodo and Comodo related certs as Untrusted (in all
>> browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
>> December 2008 from a Comodo reseller. I also have Go Daddy certs as
>> Untrusted.  This is quite a few certs.
>>
>> At the very least, SeaMonkey should warn me that it will revert all cert
>> settings to default when I upgrade but there has been no warning that SM
>> reset my settings for certificates. I only realized it when I didn't get 
>> a
>> popup warning when I went to a site that uses Comodo related certs. (Here 
>> is
>> where I prefer Opera as it handles this in an elegant, no fuss, clean, 
>> and
>> quick manner but Mozilla browsers do it in a clumsy and irritating manner
>> although in the past Mozilla handled the certs in a much superior manner
>> than now).
>>
>> I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as
>> possible so I want to be warned anytime I am about to go to one of these
>> sites.
>>
>> I have gone through every cert's settings now and Untrusted all the ones 
>> I
>> want to be Untrusted.  I'd like to avoid this with future updates.
>>
>>
>
> Some time ago, I untrusted CNNIC.  This did not change with 2.12 or
> 2.12.1.
>
> -- 
>
> David E. Ross
> <http://www.rossde.com/>
>
> Anyone who thinks government owns a monopoly on inefficient, obstructive
> bureaucracy has obviously never worked for a large corporation.
> © 1997 by David E. Ross

I don't recall this happening with past updates...just this last one. I 
wonder if it could be because I had to do a full upgrade...not the small one 
from internal update (which had the wrong files when I tried to update that 
way)? 


_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to