The protocol_factory doesn't support `Protocol`s with async handlers
e.g `async def connection_made` won't actually be awaited and thus nothing ever happens.
Now there's a pretty ugly solution with one long-ass method, but maybe that can be trimmed
or a callable can be used.
#4 - Investigate extending pr0xy to use SAM
Otherwise strings are passed and it can't start up.
Sockets can't be created when a string is passed as the port param
#4 - Investigate extending pr0xy to use SAM
The transparent proxy creates a client tunnel to the requested destination for each client connection.
This is untested for now, but a server tunnel is also incoming if this works well.
#4 - Investigate extending pr0xy to use SAM
It can get called in quick succession and overwrite assignments if the
checks aren't done at the right time
#4 - Investigate extending pr0xy to use SAM
We only want i2p to create a tunnel to the requested host on i2p.
There's no need to modify any other packets at the moment
#1 - Forward using iptables, pr0xy and custom DNS
Right now all it does is print the packet payload. Need to find out wtf
that actually is and how to treat it
#1 - Forward using iptables, pr0xy and custom DNS
- python requirements are now kept in a file and installed during build
- variables are used in exec.sh to remove magic values
- executable scripts are moved into one directory
#1 - Forward using iptables, pr0xy and custom DNS
