I2P Integration

Development
316

Please someone update that wiki page.

Meaning packages.debian.org bullsye.

1 Like
317

Most updated sources and instructions should be here: https://deb.i2p2.de/

@nurmagoz can you test and update the wiki please?

318

Please use wiki template:

usage example:
Install the Signal Desktop Client

319

Hello friends. Is there anything I can do to help this venture? I may not be nearly an expert like many, but I2P integration is very exciting to me =)

320

This: I2P Integration - #314 by Patrick

Otherwise would be good to rehash what has been discussed in this forum thread.

321

sure thing, atm I2P changing their i2p installation instructions to
match latest apt changes (deprecating apt-key) once finished i will
update the wiki:

2 Likes
322
323

done and added some improvements:

2 Likes
324

Thanks. Working well and I re-added the privoxy package in the installation instructions.

2 Likes
325

Could you please document the purpose of privoxy?

At the moment privoxy does nothing. It just listens on port 8118 and that port is no longer used on Invisible Internet Project (I2P).

Also privoxy config would have to be restored?

1 Like
326

Appended it to the step" 5. Configure Tor Browser to allow connections to I2P". Not sure you prefer this or just an obscure ref note.

1 Like
327

Still same issue.

328

In the latest update to I2P wiki, Where do you see Privoxy useful?

Privoxy now is just an extra package useless for the end user.

If privoxy can be removed then it should be removed from the wiki, And only optional choice for the end user he can install it if he want to as any other package.

1 Like
329

NOT useless. It allows for auto-redirection of special domains like.i2p and freesites to their respective daemons. Without it the UX of these alternative networks is degraded severely. Reverse any edits removing it please (if they’ve been committed).

330

Currently as of the latest revision privoxy does nothing with the instructions as is. So with the instructions as is, privoxy is doing nothing.

In https://www.whonix.org/w/index.php?title=I2P&type=revision&diff=77944&oldid=77939 @nurmagoz removed configuring Tor Browser for using privoxy with its default port 8118. Why was it removed? I guess it was removed because the instructions where dysfunctional and unmaintained at that time if I remember right? I think I tried and failed. It was probably due to Tor Browser changes.

This is the last old revision which still uses privoxy / port 8118:
https://www.whonix.org/w/index.php?title=I2P&oldid=77939

I expect re-adding privoxy to be complicated and require several hours of tinkering if it’s possible at all.

In case I am wrong… Can you currently use i2p with Tor Browser and privoxy? @HulaHoop

331

Yes those instructions were added by me recently (and were functional) when I went ahead and retested it with I2P and Tor Browser to browse eepsites seamlessly.

2 Likes
332
333

Its easy to do that, But now i just tested privoxy instructions the clearnet in TB doesnt work, But .i2p and .onion does work.

The current instructions which is without privoxy, .i2p work, and clearnet work, .onion not.

What we have common is .i2p in both working, So i dunno do you have a solution for clearnet issue + privoxy?

Otherwise .i2p working properly with current instructions, But if privoxy can solve all connections (clearnet, .i2p, .onion) then i dunno how to do that, Please test and see how to do that properly.

Note: In TB network.proxy.socks_remote_dns is now hardcoded and its reversible to always to the same state.

Asked @eyedeekay and replied:

  • eyedeekay: There are several ways to do it, one is a proxy.pac, one is to use privoxy to route everything, the last is to use containers-specific proxies in multi-account containers
  • eyedeekay: My preference is for the last because you can use the containers to enforce network boundaries, dropping I2P requests from the Tor container and Tor requests from the I2P container
  • eyedeekay: But which way is best remains to be seen
1 Like
334

So in summary…

old, last revision really using using privoxy:

  • i2p webinterface functional
  • i2p eepsites functional
  • clearnet broken
  • onion functional

current revision without privoxy [1]:
(this at time of writing)

  • i2p webinterface functional
  • i2p eepsites functional
  • clearnet functional
  • onion broken

Correct?

[1] privoxy get installed but not configured so effectively doing nothing.

Confirmed. This is true. That is also what I described here:
Tor Browser Customization using user.js (for example for i2pbrowser)

The same in other words:
network.proxy.socks_remote_dns set to true is now hardcoded directly by Tor Browser and it always reverts to Tor Browser default after Tor Browser restart.

i2p inside Whonix-Workstation instructions - both old and new - require network.proxy.socks_remote_dns set to false.

Unless the user re-applies these Tor Browser settings all the time which is very bad usability, I don’t think we currently have a good solution with or without privoxy.

1 Like
335

Yes

1 Like