Mozilla Will Block Firefox Add-Ons That Contain Obfuscated Code -

submitted by BackwardsCompatible from helpnetsecurity.com

all 5 comments
sorted by:
top
newinsightfulfun

[–]Yhvr 3 insightful - 1 fun3 insightful - 0 fun4 insightful - 1 fun -  (2 children)

Oh no, what will we ever do? cough https://beautifier.io/ cough

I mean, you can only prettify code so much. In the process of obfuscation, things like comments and variable names are lost. There are also some pros to obfuscation, like faster execution time (sometimes), and smaller files. I don't see why they should be against this

[–]cant_even 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (1 child)

Google said:

the company explained its decision by noting that over 70% of malicious and policy violating extensions that they block from Chrome Web Store contain obfuscated code.

...and Mozilla agreed.

That's good enough for me.

My crappy connection delays me more than any millisecond-faster 'execution time' could make up for.

[–]Intuit 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (0 children)

the company explained its decision by noting that over 70% of malicious and policy violating extensions that they block from Chrome Web Store contain obfuscated code.

It's flawed to think that therefore blocking obfuscated code will stop 70% of malicious and policy-violating extensions. Initially it will, of course, but those will be modified to pass as non-obfuscated code.

[–]Orangutan 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

Figures they'd do it on a Friday.

[–]m68k 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

Seems as of now, Firefox is already killing (deleting in my case) addons. At least I can fallback to Seamonkey. :P