aracapelli wrote:Thank you barbaz for your reply. On the contrary, why would you need to waste resources by having NS
protect against something that is unsupported and won't work?
If resources are that significant an issue for you, then you have much bigger problems to worry about. But if resources are the issue, when you upgrade to Firefox 53 you probably will
want to disable those protections.
Otherwise, IMO it's better to keep the protections. You won't be using those plugins, nor the plugin content. And it's no longer possible to use that stuff the way you'd want. So what do you gain from the increase in potential attack surface? Best harden the unused stuff as much as possible, because you never know what a haxxor might be able to do.
Personally, I'd be inclined to try setting "Apply these restrictions to whitelisted sites too" when even Flash gets dropped.