Feature #7725: Isolate I2P web browsing from Tor

Feature #7725

Isolate I2P web browsing from Tor

Added by intrigeri 2014-08-02 14:34:28 . Updated 2014-10-16 08:10:43 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Tails_1.2

Start date:

2014-08-02

Due date:

% Done:

100%

Feature Branch:

kytv:feature/7725-i2p-browser

Type of work:

Code

Blueprint:

Starter:

Affected tool:

I2P

Deliverable for:

Description

One thing that came up, as part of the discussion on the What to do about I2P in Tails? thread on tails-dev@ (July and August 2014), was the need to isolate I2P web browsing from similar activity over Tor. This could e.g. be implemented with a dedicated web browser for I2P, which could be very similar to the way we handle the Unsafe Browser to start with. A UX challenge will be if/how to allow sharing files between that dedicated browser and the amnesia user.

Subtasks

Related issues

Related to Tails - Feature #6039: Research consequences of Torbrowser patches when using I2P	Confirmed
Related to Tails - ~~Feature #7732~~: Start I2P automatically when requested at the boot prompt	Resolved	2014-08-03
Related to Tails - ~~Feature #7976~~: Disable LAN access in Tor Browser	Resolved	2014-11-05
Related to Tails - ~~Bug #7951~~: Refactor code for task-specific browsers	Resolved	2014-09-26
Blocked by Tails - ~~Feature #7542~~: Decide whether we migrate to the Tor browser in time for FF31	Resolved	2014-07-10
Blocks Tails - ~~Bug #7948~~: Only show I2P bookmarks in the I2P browser	Resolved	2014-09-25

History

#1 Updated by intrigeri 2014-08-02 14:41:07

related to Feature #6039: Research consequences of Torbrowser patches when using I2P added

#2 Updated by intrigeri 2014-08-03 13:52:46

related to ~~Bug #7722~~: Make I2P harmless unless enabled on the kernel command-line added

#3 Updated by intrigeri 2014-08-03 13:54:49

related to deleted (~~~~Bug #7722~~: Make I2P harmless unless enabled on the kernel command-line~~)

#4 Updated by intrigeri 2014-08-03 13:54:56

related to ~~Feature #7732~~: Start I2P automatically when requested at the boot prompt added

#5 Updated by kytv 2014-08-08 17:31:42

% Done changed from 0 to 20

Would you be opposed to having this second browser send non .i2p traffic to Tor as is done now? In my workspace I re-enabled the I2P outproxies so that all traffic in the “I2P Browser” will be I2P’s problem.

I should have something for public testing “soon”. (I’m already testing this browser and the associated NetworkManager hooks (for starting I2P) locally).

#6 Updated by intrigeri 2014-08-08 21:00:47

> Would you be opposed to having this second browser send non .i2p traffic to Tor as is done now?

I personally would be opposed, as it defeats the goal of keeping Tor activities relatively immune to deanonymization vulns in I2P (and maybe vice-versa, by the way, but Tails depends so much on Tor that I’m not sure it works that way).

> Otherwise I’ll re-enable the I2P outproxies so that all traffic in the “I2P Browser” will be I2P’s problem.

I’d rather see the “I2P Browser” only support eepsites, at least for its first iteration. Anything else will require more thought and discussion.

> I should have something for public testing “soon”. (I’m already testing this browser and the associated NetworkManager hooks (for starting I2P) locally).

Woohoo, great to hear :)