TomBombadil wrote:Thanks to your suggestion I found this recent
font vulnerability fixed in Firefox 42 or 43, but I'm not sure that it affects Firefox for Android.
I think one would need to know the name of the problematic font rendering library and check whether it is in the multiplatform core of Firefox or Windows-specific. If the library is really about rendering though, then it may be in Gecko, and as far as I know Firefox for Android uses Gecko, soooo, probably, fonts should be disallowed on Android too.
Agreed, but I'm just a power user. Other members of forum staff (especially Giorgio) would be able to give a more informed assessment.
TomBombadil wrote:I wonder if Chrome has this issue with fonts too now.
If was fixed
in Firefox, then I would expect Chrome wouldn't have the same exact vuln, although if they're using the same font rendering backend it's very possible it'd have a similar vuln. (in short, idk)
Again, Internet searches are the best way to judge how paranoid you should be about webfonts...
TomBombadil wrote:unusual protocols like jar: (to be removed in Firefox 45 because unsafe).
Bug link please?
TomBombadil wrote:I'm going to assume data: and javascript: are tied to the Script category though.
µMatrix is a network filter, it should have no effect on data: URIs. I would think that whether or not javascript: URIs permissions are controlled by the script category would be controlled by whether or not µMatrix blocks inline scripts, and IIRC it does (I don't use µMatrix's script blocking at all though, I prefer leave that entirely to NoScript).
TomBombadil wrote:The same person can't ask for everything in one go or all of it will be ignored,

I would hope gorhill isn't that kind of person, that he would get to all of it that he finds reasonable as he has time...
TomBombadil wrote:Last question, do you guys enable fonts selectively with Javascript ? I got the idea that the library had been made in a very unsecure way and way more unsafe than the Javascript engine, and so allowing JS was less of a risk than allowing fonts. I guess my original question was, are the risk levels evened out nowadays ?
I'm not sure quite what you're asking, so I'll paraphrase my best guess and then answer that: "Do you guys configure NoScript to (by default) un-block fonts when Allow or Temporarily allow a site's JS?"
I can only speak for myself here, and my answer is yes. This is not so much a technical question as it is a question of trust. In Internet security, either you trust a site or you don't.. (i'll skip the explanation of this as you seem knowledgeable enough not to need it

) Active content is a requirement to exploit almost all browser vulnerabilities, including even e.g. CSS vulns. If I trust a site to run JS, I am trusting that they won't do anything nasty like exploit a vulnerability, as such I would have no reason to disallow them from displaying the [self-hosted] font(s) they want (unless, of course, said font(s) make my eyes bleed

).
Just my 2¢, YMMV.