Michael Lefevre wrote:Whitelisting of a few trusted certificates in the default iinstallation
That makes sense.
But the problem is that, given a few trsusted certificates, there needs to be a mechanism to distribute trust. This basically means that the trusted sites will have to sign third party code. Assuming they don't have the resources to do code review, it seems unlikely that people will want to sign code they haven't verified.
Of course, the same situation exists with whitelisting sites, but:
a) It's easier. There's no need for people to contnually ask for signatures
b) The implicit trust from an extension being on a whitelisted site is less than that from a extension having been signed by a trusted site.
Sorry, that's not clear. Whitelisting is easier than asking for signatures all the time.
_______________________________________________
Mozilla-security mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-security
