NoOp schrieb:
Per the Thawte instructions, I use on IE on Windows to manage my certs.
Does this means that anyone running on a Mac or on Linux is left out in
the cold?
There is no impact on using SM, except for the process when SM checks
itself for updates.
Right... Does mozilla.org not have a valid cert? You guya are now adding
GeoTrust& Thawte certs so that you can do SeaMonkey updates?
As Justin explained, they don't have a valid certificate, but several.
That's the point. ;-)
This is about root(!) certificates.
Not being a SM developer, but from reading the posts and the bug:
This change does not affect any certificate handling in SM for normal
operation. It does not affect user certificates, web site certificates,
email certificates, or whatsoever.
It's just about having 3 (instead of 1) "root"(!) certificate being
allowed to sign valid certificates for servers (I assume) holding the
information about updates.
It may always happen that the issuer of a root certificates has any kind
of problems (financial, security, physically, politically...) so having
more than one alternative "root" is a good precaution in itself.
When Justin states, that they already have changed their certification
authority for their new own certificates, than this change is critically
important. How urgent it is, you only know, when looking at the expiry
dates of the old ones. ;-)
So, this is a trivial change (from code point of view) with no direct
user impact except for ensuring the reception of updates in the
coming... months, I guess.
That's exactly what Robert wrote.
So, what's the point?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
