Feature #6534

Adapt fingerprinting documentation to I2P

Added by sajolida 2013-12-23 12:07:45 . Updated 2017-07-10 22:02:00 .

Status:
Rejected
Priority:
Low
Assignee:
Category:
Target version:
Start date:
2013-12-23
Due date:
% Done:

0%

Feature Branch:
bitingbird:doc/6534-fingerprint
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
I2P
Deliverable for:

Description

Our fingerprinting documentation (https://tails.boum.org/doc/about/fingerprint/) does not mention I2P. Now that I2P is maintained, we should update this page to be less Tor-centric.

Subtasks

History

#1 Updated by intrigeri 2014-06-21 15:19:44

  • Category set to 180

#2 Updated by BitingBird 2015-03-15 23:17:53

  • Assignee set to BitingBird
  • Target version set to Tails_1.4

#3 Updated by BitingBird 2015-04-05 14:35:53

  • Status changed from Confirmed to In Progress
  • Feature Branch set to bitingbird:doc/6534-fingerprint

#4 Updated by BitingBird 2015-04-05 15:03:18

  • Assignee changed from BitingBird to sajolida
  • QA Check set to Ready for QA

It is impossible to adapt this page, as it is really Tor-centered, and there is no equivalent documentation about i2p. So I just added a paragraph saying that it is specific to Tor, and doesn’t apply for i2p.

Built, looks good - please review & merge :)

#5 Updated by sajolida 2015-04-24 08:22:03

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Info Needed

I’m not satisfied by the phrasing “the fingerprinting situation is
different” which is clearly as vague as possible. What do you mean by
that? Do you have any precise information regarding that?

If so, could you add them to this ticket so we can check whether they
could be explained a bit more.

Otherwise, could you get in touch with I2P upstream, or maybe kytv, to
get more precise information.

For the time being, the current page isn’t wrong I think as it makes it
clear that we are taking about Tor. Or at least your vague addition
doesn’t bring more information.

Ah, and if you start working more on this page, please start again from
master as you introduced unjustified wrapping on 80% of the page and
review will be very hard if you start modifying it.

#6 Updated by BitingBird 2015-04-25 05:53:37

The only more-or-less relevant page on their documentation is https://geti2p.net/en/comparison/tor and I’m unable to make something of it…

#7 Updated by sajolida 2015-04-26 07:26:43

Me neither :)

If you want to continue investigating this, you could try to perform the usual website fingerprinting tests that we do on Tor Browser and compair the results of the I2P Browser (https://panopticlick.eff.org/ and http://ip-check.info).

#8 Updated by BitingBird 2015-05-04 12:53:42

  • Target version changed from Tails_1.4 to Tails_1.4.1

#9 Updated by BitingBird 2015-05-21 19:02:02

  • Target version changed from Tails_1.4.1 to Tails_1.5

#10 Updated by BitingBird 2015-07-04 05:57:46

  • Target version changed from Tails_1.5 to Tails_1.6

#11 Updated by BitingBird 2015-08-05 08:05:12

  • Target version changed from Tails_1.6 to Tails_1.7

#12 Updated by BitingBird 2015-11-17 09:59:04

  • Assignee deleted (BitingBird)
  • Target version deleted (Tails_1.7)

Not going to work on this.

#13 Updated by Anonymous 2017-06-29 10:13:06

  • Priority changed from Normal to Low

lowering priority as we don’t ship I2P currently.

#14 Updated by sajolida 2017-07-10 22:02:00

  • Status changed from In Progress to Rejected
  • QA Check deleted (Info Needed)

Rejecting as we don’t ship I2P anymore so there’s nothing to document.