discuss "i2p"

[nadir]

which is here

[nadir]

i got a bit of problems to run tor and i2p, so i wrote down the settings for foxyproxy, used by tails:

apt-get install foxyproxy

1) i2prouter console
a)General
Enabled: yes
Name: i2p router console
Animate: yes
Include: yes
Perform: yes
b)Proxy Details
Direct Internet connection: yes
c) URL Patterns
Enabled: yes
Pattern name: i2p router console
Pattern: ^http://(localhost)|(127.0.0.1):7657(\.*)?
(wildcard contains -> regular expressions)
Whitelist

2) i2p
a)General
Enabled: yes
Name: i2p
Animate: Yes
Include: yes
Perform Dns: yes
b)Proxy Details
Manual Proxy Configuration: 127.0.0.1 4444
Socks v5
c) URL Patterns
Enabled: yes
Pattern Names: i2p
Pattern: ^https?://[^/]+\.i2p(:[0-9]{1,5})?(/.*)?
(wildcard contains -> regular expressions)
Whitelist

3) tor http(s)
a) General
Enabled: yes
Name: Tor http(s)
Animate: yes
Include: yes
Perform: yes
b) Proxy Details
Manual Proxy configuration: 127.0.0.1 8118
Socks v5
c) URL Patterns:
Enabled: yes
Pattern Name: http(s)
URL Pattern: ^https?://.*
(pattern contains -> regex)
Whitelist

4) tor ftp
a) General
Enabled: yes
Proxy Name: tor ftp
Animate: yes
Include: yes
Perform: yes
b) Proxy Details
Manual Proxy Configuration: 127.0.0.1 2121
Socks v5
c) URL Patterns:
Enabled: yes
Pattern Name: ftp
URL Pattern: ^ftp://.*
(pattern contains -> regex)

5) Default
a) General
Enabled: greyed out (how?)
Include: yes
Perform: yes
b) Proxy Details:
Manual Proxy Configuration: 127.0.0.1 9050
Socks: yes
Socks v5

Strange stuff, i wish i would understand it better.
Any hints or help on that problem is much appreciated.
(for me, now and here, setting it manually in iceweasel's settings is ok, but in the long run...)

Edit:
I changed ^ftp.//.* to ^ftp://.*

[dbbolton]

My approach (instead of installing the ubuntu deb):

Code: Select all

print 'deb-src http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu natty main' >> /etc/apt/sources.list
aptitude update
mkdir i2p; cd i2p && apt-get source i2p && cd i2p-0.8.8+repack
dch -l +dbb


dch will spawn $EDITOR. I changed the release to 'unstable' and added a comment (DEBEMAIL and DEBFULLNAME are added automatically). :wq

There is a bug in "debian/rules". Change

Code: Select all

 rm -f core/c/jbigi/*.[s]o

to

Code: Select all

rm -f core/c/jbigi/*.{s,}o

This is to remove all .so and .o files. Otherwise, the build may fail due to the untracked binary file "i2p-0.8.8+repack/core/c/jbigi/jbigi.o".

Finally

Code: Select all

dpkg-buildpackage -rfakeroot -us -uc
dpkg -i ../*.deb


Code: Select all

apt-cache policy i2p
i2p:
  Installed: 0.8.8+repack-2ppa1+dbb1
  Candidate: 0.8.8+repack-2ppa1+dbb1
  Version table:
 *** 0.8.8+repack-2ppa1+dbb1 0
        100 /var/lib/dpkg/status


My changes don't really do anything. I just sleep better at night knowing that I didn't install a package directly from an Ubuntu PPA.

[nadir]

Thanks, dbbolton, that will help me a lot.
To stress is: i was speaking of a test-box where to do it, not on your daily ride box.


----------------------
I have made a remix of refracta and added i2p including the foxyproxy settings above.

Code: Select all

wget http://minus.com/d4hrBs4eqTEIq.iso

fsmithred tested, said the download takes a few minutes and it worked (it booted)


It is based on refracta, and elder release, and hence comes with xfce4/icewm and the refracta tools (installer, snapshot, repsit, taskfer, etc), a few scripts in /home/user/bin and i installed:

Code: Select all

i2p
tor/polipo
foxyproxy
scuttle
wordpress
zim
osmo
gobby

It should run full-screen with guest-additions enabled in Virtualbox.
I was not sure how much space i needed to make it fit on a CD, so some basic desktop stuff (gimp) is missing. Same for sound.


If you want to use zim and osmo to be rsynced on your server you need to
server:

Code: Select all

mkdir ~/Documents/Zim_Notes ~/.osmo

client
edit /home/user/bin/mount_zim and replace the placeholder "your_user_name" with your user name at the server.
edit /home/user/.ssh/config and make the changes mentioned there (LAN-IP of server, username of server, port and name of ssh-key)
add your ssh-key, the one to access the server, to ~/.ssh/
There is an icon in the panel, to mount_zim, but i can't promise it will work.

All user-names (login, wordpress, scuttle) are "user", all its passwords are "user"
All root-names are "root" (system, mysql-root, scuttle-database, and all its passwords are "root".
The ssh-key, default, in /home/user/.ssh password is "refracta". You can delete it and replace it.

Be patient when iceweasel starts.
Boot might (!) be slow, at least in Vbox. Hunt for prunes while it boots.
The home page localhost might be broken. If so disable tor and foxyproxy to use it.
In ~/bin/plexus.pl you will find plexus, a script by dbbolton, to create websites on the fly (static-site-generator like), just in case you don't like localhost

This is just a test. Nothing for serious usage.
Just to have a short look, to fiddle a bit. The very raw direction i (!) would take for a freedombox server (and many, many things are missing).
Here we got servers/clients on one box, sure.
I smashed it together in a day, with refracta as a base that is rather easy, but it gives you the idea that you might run into inconveniences.

PS: holy big-bang, how could i miss that:
It is free as in freedom. vrms is proud.

[nadir]

looks like after the russian invasion a couple of weeks ago i2p is getting more and more active.
Anyway, i found a site which lists a couple of interesting links:
http://cheech-wizard.i2p/wizdum.html#links
(finding really usefull sites is still a daunting task... make sure to bookmark good sites; once you found a good one...)

-------------------
In case you don't run i2p (yet...), but want to check a few sites:

But you can go look up your eepsite address at www.awxcnx.de/tor-i2p-proxy2-en.htm, and follow the link to your eepsite. This will take you out over the public Internet, and back into i2p space via a proxy

[nadir]

Not sure if anyone is listening, so i can go on talking about things i don't really understand.
If you got i2p running on one box and want to access it from another you can use ssh-tunneling
(besides other things, but that seems like an easy solution):
quote:
To tunnel I2P through SSH create the necessary tunnels by either running

Code: Select all

'ssh -L7657:127.0.0.1:7657 -L4444:127.0.0.1:4444 $USER@$SERVER'

or setting the LocalForwards in your ~/.ssh/config accordingly.
end quote.
Then open localhost:7657 in your local webbrowser and foo: you are connected.
If you got IRC running for i2p channels you will need to add: -L6668:127.0.0.1:6668
More about the subject of ssh tunnels here:
http://www.debian-administration.org/ar ... y_with_SSH

If you want to run privoxy, tor and i2p on the other machine and access it, you will need to tell me how that works.

I found another good list of links:
http://theanondog.i2p/cgi-bin/eepsites.py which i add to the one given above:
http://cheech-wizard.i2p/wizdum.html#links
I found also a git site and pretty much all else one can dream of (especially when it's broken it is more of a dream than anything else).

[nadir]

How to set up your own i2p-server (kinda web-server, but not on the web

Summary of what i think i did.
Might contain typos and other errors.
It is a bit too detailed, but i ran across lots of infos/how-to's which skipped important parts.



0) Overview
You need a server with ssh-access, privoxy, tor and i2p
You sshforward i2p-router and privoxy port to access the webinterface locally
You copy the website to the server, ~/i2p/eepsite/docroot
You set up the webserver jetty in the i2prouter-console, I2PTunnel
Finally you will have to announce it to the i2p world.

1) What you need:
a) a 24/7 machine
b) ssh-access to it, and the knowledge involved
c) an existing website (index.html)
d) bit of time, bit of headeaches (seriously)



2) On the server side

Code: Select all

ssh me@server

and

Code: Select all

apt-get install privoxy tor i2p

edit /etc/privoxy/config, and append:

Code: Select all

forward-socks5 / 127.0.0.1:9050 .
forward-socks5 .onion 127.0.0.1:9050 .
forward .i2p localhost:4444

Restart privoxy

Code: Select all

/etc/init.d/privoxy restart

edit ~/.i2p/clients.config and make this line:
clientApp.4.startOnLoad=true
like this:

Code: Select all

clientApp.4.startOnLoad=false

The comment says it all: if you start i2prouter it won't try to open a web-browser
(if you don't make that change the web-browser simply won't start, it seems, but i changed it anyway)

Code: Select all

i2prouter start

Code: Select all

exit

the ssh to the server

You will probably want to forward the port you find at:
i2p-router-console, left panel -> I2PServices, Network
from your network router (with usual port-forwarding).



3) On the client site

If you got them installed:

Code: Select all

/etc/init.d/privoxy stop
/etc/init.d/tor stop
i2prouter stop

Code: Select all

ssh -L7657:127.0.0.1:7657 -L8118:127.0.0.1:8118 -L6668:127.0.0.1:6668

which are the ports for the i2p-router, for privoxy and for i2p-irc

open iceweasel/firefox, menu-bar -> Edit -> preferences -> advanced -> network
set it to make use of
127.0.0.1 and port 8118
(which is just the same as if you would be running privoxy locally. If you had that, keep as is.
I am not sure if 127.0.0.1 or localhost is of importance, i am not sure about the need to clear the cache or restart iceweasel.
That takes a bit of fiddling. Looks like it suddenly would work. Patience won't hurt).

open an arbitrary website to check if you still got internet access:
https://duckduckgo.com
Once here enter
"am i using tor?
and click on
https://check.torproject.org/
If you don't use tor
a) fiddle with the settings of iceweasel. If that doesn't help:
b) exit the ssh connection and run the ssh command again
Hopefully it won't take to long to get it sorted.


4) the path for an eepsite (~/.i2p/eepsite/docroot)
rsync your existing website (index.html, css directory, whatnot to the server)
I first copy it to the existing folder /home/me/Temp at the server:

Code: Select all

rsync -ruv index.html css me@server:Temp
ssh me@server


Make a backup of the existing eepsite It contains a good docu

Code: Select all

cd ~/.i2p/eepsite
cp -r docroot docroot_original

Copy your site in place:

Code: Select all

cd docroot
cp -r ~/Temp/{index.html, css} .

5) go back to the web-browser at the client
open the i2prouter
http://127.0.0.1:7657
In the left panel click on
I2PTunnel
Then click on
I2P webserver
click on Auto Start(A): (Check the Box for 'YES')
Enter a name you like (all lower case, ending with .i2p) at:
Website name(W): h4xsor.i2p
and copy the __complete__ Local destination(L):
Scroll down and click on "Save"


6)
Go back to the router-console
http://127.0.0.1
and click on Addressbook, then master
Enter the name of your eepsite
h4xsor.i2p
and the Local destination just copied from the I2PTunnel.
click on save

You should now be able to access your eepsite yourself (but the world does not know about it, yet).
As we didn't ssh-forward port 7658 with ssh, you can't access it from the link "Website" at the routepage (7657)
Either use your name "h4xsor.i2p", or go to
router-console, I2PTunnel, and click on "Preview".



7) Inform the world
How to let the world know about your haxing skills eepsite, dealing with cain&abel, john the ripper and all the other loi-c-ool tools, i will add later
(mainly cause i don't know it yet. It is mentioned in said original eepsite we backed up earlier).
Edit: As far i see go here:
http://stats.i2p/i2p/addkey.html
enter your i2p sites name and the Local destination(L), to be found at the I2ptunnel-manager.
Announce it here too:
http://forum.i2p2.de/viewforum.php?f=16 ... 04695ec4c5
_after_ you read the sticky.

All as far i can tell.

[FretfulMother]

I upgraded LullySec to Wheezy:
http://sourceforge.net/projects/lullyse ... =directory
Don't expect anything.
It might not boot for you.
It might boot, but won't work (tor or i2p or both).
It might seem to work, but leak info behind your back.
It is just quick and dirty, for the fun of it. refractasnapshot is used to create it.