[tor-bugs] Re: #1328 [Tor-Torbutton]: Add option to block remote fonts

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1328: Add option to block remote fonts
-----------------------+----------------------------------------------------
 Reporter:  mikeperry  |         Type:  enhancement  
   Status:  closed     |     Priority:  minor        
Milestone:             |    Component:  Tor-Torbutton
  Version:  1.2.4      |   Resolution:  wontfix      
 Keywords:             |  
-----------------------+----------------------------------------------------
Changes (by mikeperry):

  * status:  new => closed
  * resolution:  None => wontfix


Old description:

> Firefox 3.6.1 recently fell prey to a remote font exploit. In firefox
> 3.5, the browser began accepting fonts
> remotely from websites. The problem is that the truetype font engine is
> ancient code - code rewritten
> from pascal into non-reentrant C, and then rewritten again into reentrant
> C. This code is extremely cryptic
> and hard to maintain and review, and probably wasn't written with the
> threat model of unsafe and malicious
> remote input in mind. It's a security nightmare waiting to rain down more
> vulnerabilities like this.
>
> My personal feeling is that this means we should ship with NoScript in a
> good default configuration for
> Tor Browser Bundle. However, I would be willing to accept patches to our
> nsIContentPolicy to optionally
> block remote fonts as an alternative.
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 Firefox 3.6.1 recently fell prey to a remote font exploit. In firefox 3.5,
 the browser began accepting fonts
 remotely from websites. The problem is that the truetype font engine is
 ancient code - code rewritten
 from pascal into non-reentrant C, and then rewritten again into reentrant
 C. This code is extremely cryptic
 and hard to maintain and review, and probably wasn't written with the
 threat model of unsafe and malicious
 remote input in mind. It's a security nightmare waiting to rain down more
 vulnerabilities like this.

 My personal feeling is that this means we should ship with NoScript in a
 good default configuration for
 Tor Browser Bundle. However, I would be willing to accept patches to our
 nsIContentPolicy to optionally
 block remote fonts as an alternative.

 [Automatically added by flyspray2trac: Operating System: All]

--

Comment:

 Closing this. We should rely on NoScript.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1328#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online