Hello,
Is there any reason to keep block the font-face objects while there is the OpenType Sanitizer in firefox?
Maybe a new filter based on[1] can be added to match chrome level?
I don't quite understand the filter mechanism of noscript, as it is based on mime type, so for this it cannot be used as site can send whatever mime for font.
Alon
[1] http://code.google.com/p/ots/source/browse/trunk/README
OpenType Sanitizer
OpenType Sanitizer
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20100101 Firefox/10.0.4
Re: OpenType Sanitizer
Is there any reason to get rid of it, as another layer of defense-in-depth, in the event of bugs in Fx OTS (they have occurred)?alonbl wrote:Is there any reason to keep block the font-face objects while there is the OpenType Sanitizer in firefox?
You can uncheck it, should you like.
If you wish, every time you encounter a new MIME type for font, you can add it to an ABE rule. ABE FAQI don't quite understand the filter mechanism of noscript, as it is based on mime type, so for this it cannot be used as site can send whatever mime for font.
Code: Select all
Site somenewfontmime@https?://*./
DenyMozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/12.0