Quick update: For those who don't know, i2p.rocks has a federated jabber server with open registration (for now) and is available on i2p, via ynkz7ebfkllljitiodcq52pa7fgqziomz4wa7tv4qiqldghpx4uq.b32.i2p:5222 (the port is important).

This blog is now also reachable via i2p here

With i2lua you can add custom logic to your Invisible Internet router by writing scripts in Lua.

Lua is a full-featured programming language, which means you can resolve complex issues with it.

Some basic tasks you can accomplish with i2lua:

• make all tunnels to have only trusted nodes as first hop (restricted routes, similar to Tor's guard nodes)
• make I2P router to only use high-speed nodes for building tunnels
• create tunnels with first hop in specific countries (e.g. make connections only to Russia and Germany)
• implement custom node profiling mechanism

and so on.

Example script for i2lua

This is a quick howto guide on setting up a very minimal git repo for sharing code inside i2p using any modern linux distro. (What is git?)

Please note this is not a general git tutorial, you will need to know a little git.

Simple setup

Git proxy settings are easy, it's deep in the man pages but usually there's no need to set them it seems daunting.

For all this you'll need ssh, git, connect-proxy and i2pd (see here for i2pd)

For ubuntu xenial (root needed)

1
2
3

wget https://github.com/PurpleI2P/i2pd/releases/download/2.8.0/i2pd_2.8.0-1xenial1_amd64.deb -O i2pd.deb
dpkg -i i2pd.deb
apt install ssh git connect-proxy

Client side

(The following should be run as your regular user)

Create a shell script for proxying over i2p, 127.0.0.1:4447 is i2pd's socks proxy, it's enabled by …

Read more ...

i2p.rocks inproxy will be done again until I get a chance to rewrite the in proxy app server in full, the nginx configuration I was using stopped working as of nginx 1.10.

The source code is on github here, feel free to help out.

This project is not a very high priority and i2p.rocks will be back up once this rewrite is done.

(this guide is probably out of date)

I have recently successfully built i2pd for the raspberry pi using a cross compiler on Ubuntu 16.04 LTS for amd64. So far i2pd has an uptime of over a week with no crashes or memory leaks running a small irc server. There are still a few things i2pd could do better, specifically more documentation but I digress.

Building

First off if you don't have git install it along with the basic compiler stuffs.

1

$ sudo apt install git build-essential

To build a static i2pd for raspberry pi you'll need to build an environment with all the i2pd dependencies. We'll use ubuntu's gcc arm cross compiler for this.

1

$ sudo apt install g++-arm-linux-gnueabihf gcc-arm-linux-gnueabihf

We don't want to mix the libraries we are going to build with our system libraries as they are for ARM not x86 so we'll make a separate …

Read more ...

i2p.rocks in proxy is now back and powered by i2pd, a pure C++ i2p router implementation.

In time I may also provide an i2pbote gateway as well.

contact me if there is any trouble with the in proxy on jabber via jeff@rows.io

donate bitcoin to keep the in proxy alive: 15yuMzuueV8y5vPQQ39ZqQVz5Ey98DNrjE

This morning I woke up with no network connection on my desktop. After checking the ports and doing systemctl restart networking a few times I finally got online. Don't get me wrong, I want a 'one golden standard' for the Linux userland, I just don't want SystemD. With SystemD it's the little things that make the experience painful, you know, fucky network connectivity, no keyboard access before you can unlock your disks when you use FDE, loosing both X and tty when X crashes. The supporters of SystemD say it's going to get better, I know they are right, but given the direction SystemD is going it's going to get a LOT worse before it gets any better (cough systemd merging su cough).

SystemD has been a regression in the Power User experience at least for me. GNU has lost its edge, perhaps it's too late for redemption. I'm done …

Read more ...

Yay the continuation of the nntpchan blogs is here, part 2 specifically, probably more to come when things go down. In my last blog I talked about the history of overchan, specifically why it came to be but did not really touch on how it came to be.

There was never one single reference implementation for overchan, it was designed in a way so that the implementation doesn't matter so long as it can speak NNTP properly. Everyone on overchan ended up using SRNd because no one else had their source code accessable, there was on written in haskell but I could never find the source code for it. It's entirely possible that one could use INN2 with a webserver running perl cgi scripts to generate articles and markup and you'd have a compliant overchan setup. I really wish they used another name for overchan since it's already a thing …

Read more ...

After some downtime, I finally got around to restoring my blog since there's something to talk about.

I have been working on rebasing some software for a decentralized imageboard so that it can work with clearnet.

Wait wat? Here's The backstory.

In the beginning, there was Torchan. Rather, there was a version of Torchan that didn't permit that content. ( *cough*seepea*cough* ). It was according to the original host, most likely the largest tor only imageboard at the time. After a series of DoS attacks, internet drama, vps bills piling up, the original host decided to hand off the site and the private keys to someone else. What happened after that caused the desire to create an imageboard that is invulnerable to any kind of global power grab. The new host, initially using the nym "dgft", didn't want to play nice. The new moderation team effectively made the site absolutely …

Read more ...

i2p.rocks now uses self signed ssl, check the signed proof

check out this great guide for PFS with ssl here