Bug #11000

The Tor Browser's font fingerprinting protection does not work in Tails

Added by anonym 2016-01-26 17:36:53 . Updated 2016-02-13 14:22:11 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.0.1
Start date:
2016-01-26
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

As reported by Panopticlick during the manual test session for Tails 2.0.

Subtasks

Related issues

Related to Tails - Bug #11124: Update TorBrowserTailsRoadmap.png image Resolved 2016-02-13

History

#1 Updated by anonym 2016-01-26 17:58:23

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:2af53484fd7503d3888aa738d0b16ce287d33b55.

#2 Updated by anonym 2016-01-26 17:58:57

  • Assignee deleted (anonym)
  • QA Check set to Pass

bertagaz tested my fix.

#3 Updated by cypherpunks 2016-01-29 14:48:07

The Tails 2.0 release announcement says “Tor Browser 5.5 introduces protection against fingerprinting but due to an oversight it is not enabled in Tails 2.0.”

While the full story might be apparent to advanced users who click through to this issue, to everyone else, this statement is alarming and misleading because most of Tor Browser’s fingerprinting defenses are still enabled and should work fine. (I suggest s/introduces protection against/introduces new protection against font/ to make this statement accurate.)

Also, the Known Issues page says “There are currently no known differences between the fingerprints of Tor Browser inside and outside of Tails.” which is inaccurate due to this issue and the fact that AdBlock plus is enabled by default.

thanks for Tails, HTH, HAND!

#4 Updated by sajolida 2016-02-01 10:16:28

I added this to the ‘Known issues’ page. We should revert f942b67 when release 2.2.

#5 Updated by intrigeri 2016-02-04 11:06:54

  • Status changed from Fix committed to In Progress
  • Assignee set to sajolida
  • % Done changed from 100 to 90
  • QA Check changed from Pass to Dev Needed

sajolida wrote:
> I added this to the ‘Known issues’ page. We should revert f942b67 when release 2.2.

Any reason not to do that on the stable branch, so that we’re done here and everything is automatically in order for next release (if it’s an emergency one, we’ll be happy not to have to think about such things at release time)?

#6 Updated by sajolida 2016-02-05 13:04:44

  • Status changed from In Progress to Fix committed
  • Assignee deleted (sajolida)
  • QA Check deleted (Dev Needed)

That’s smart! Done in 0ecf55a.

#7 Updated by bertagaz 2016-02-13 14:22:11

  • Status changed from Fix committed to Resolved
  • Target version changed from Tails_2.2 to Tails_2.0.1
  • % Done changed from 90 to 100

#8 Updated by bertagaz 2016-02-13 16:22:58

  • related to Bug #11124: Update TorBrowserTailsRoadmap.png image added