Re: Helping ensure privacy + security

On 12/5/15 10:25 AM, [email protected] wrote:
> To say you removed it because of "extra complexity" is a weak excuse. After all will not the code be removed anyway when the big change happens, if I understand it correctly. So why the hurry of removing that code now?
> I fail to see a valid point here based on this thread.

I removed the feature (which I originally implemented) because:

1. It broke real websites.
2. It provided very little privacy benefit.
3. It provided zero security benefit against plugin vulnerabilities 
(because the hidden plugins are still enabled and accessible to any 
website).
4. The code added extra complexity required to manage multiple lists of 
plugins (hidden and visible) even though the feature was disabled (see 
#1) and could not be re-enabled.

Yes, Firefox's NPAPI code will eventually be removed, but that's more 
than a year away. Even after NPAPI support is removed, Firefox must 
retain some of that code to continue supporting Flash.

I do not plan to spend any more time on this feature. It is a dead end. 
But you are welcome to submit patches for someone else to review. My 
original patches are still accessible in Bugzilla.

chris