Jean-Marc Desperrier <[EMAIL PROTECTED]> writes: >Peter Gutmann wrote: >> How will you know which plugin(s) to disable? How will you prevent yourself >> from being sued by the creators of the plugin(s), who haven't violated the >> CA's TOS and therefore have no basis for having their plugins revoked?
>Didn't I say earlier we want a TOS that says MoFo has the final say on >revocation motives, if you don't like, don't develop extensions for >Firefox ? A ToS still doesn't tell you which plugin to disable. If spyware appears on the system and there are 30 plugins present, which one do you disable? How do you know it was a plugin at all, and not a browser security hole? Or a port 135/445 worm? Or something that came in via a million other infection vectors? A ToS saying you can disable plugins is about as effective as legislation saying you can arrest spammers (CAN-SPAM), you can't disable what you can't identify. Peter. _______________________________________________ mozilla-crypto mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-crypto
