Re: Plugin whitelist

On 3/3/2014 11:43 AM, Benjamin Smedberg wrote:
> On Friday Chad posted and blogged about our proposed plugin whitelisting 
> policy.
> 
> https://wiki.mozilla.org/Plugins/Firefox_Whitelist
> https://blog.mozilla.org/security/2014/02/28/update-on-plugin-activation/
> 
> The primary goal of this policy is to give plugin vendors who are 
> working on moving towards HTML5 solution some additional time to make 
> the transition, as well as providing feedback from plugin vendors to our 
> web API teams about features missing from the web platform. We will 
> continue to preserve user security by keeping engineering and QA 
> contacts for each plugin vendor.
> 
> Please ask questions/provide feedback by replying to 
> mozilla.dev.tech.plugins.
> 
> --BDS
> 

Can users whitelist plugins that are identified in the user's Helper
Applications list?  Will this be automated?

Can I whitelist plugins globally instead of for specified URIs?  I have
some plugins that are used by a large number of Web sites.  It appears
that the AVG SiteSafety plugin (npsitesafety.dll) operates on ALL Web
sites.

My concern is about non-Mozilla developers who do not want to bother
with applying for whitelisting but whose products are quite useful.

-- 

David E. Ross
<http://www.rossde.com/>

On occasion, I filter and ignore all newsgroup messages
posted through GoogleGroups via Google's G2/1.0 user agent
because of spam, flames, and trolling from that source.