Author: Kill Your TV Date: To: tails-dev Subject: Re: [Tails-dev] I2P & Tails 1.2 (0.9.15, browser, network-manager)
On Thu, 18 Sep 2014 16:40:29 +0000 (UTC)
intrigeri <intrigeri@???> wrote:
> > Great! Note that this code probably depends on what browser we
> > happen to ship in Tails 1.2. There are chances that we ship
> > something based on the TBB tarball, so some paths etc. will likely
> > need to be adapted.
"Porting" it should be pretty straightforward. Once I see the new branch
appear I'll rebase my i2pbrowser stuff on top of it to make the diffs
easier to review and to make the "porting" easier to manage.
On Thu, 18 Sep 2014 18:41:37 +0000 (UTC)
Patrick Schleizer <patrick-mailinglists@???> wrote:
> Glad to hear you are working on this!
>
> Wondering, wouldn't it anonymity wise be a good idea to also use (a
> separate) Tor Browser for browsing i2p?
As I see it:
1) Tor Browser for Tor. There will be no I2P or I2P router console
access because the I2P rules will be removed from FoxyProxy.
2) Tor Browser for I2P but themed a bit differently just as the
'unsafe-browser' is.. Only I2P "eepsites" (http proxy
127.0.0.1:4444), the router console (127.0.0.1:7657), and the
"local eepsite (127.0.0.1:7658) will be accessible from within
it. The I2P outproxies will remain disabled. Anything not explicitly
enabled (proxy on 4444, http on 7657 & 7658) will be dropped.