Re: [tor-talk] Transparent proxy question

2016-03-08 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben Tasker : > Afaik, no. But you could configure the remote machine to transparently > proxy and then on your router configure interesting traffic to use that as > a gateway - I use Policy Based Routing to direct port 80 traffic to my > squid box and

Re: [tor-talk] Transparent proxy question

2016-03-08 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aeris : >> I mean, I could write something like that myself, but maybe >> there is a ready made solution? > > I already dev a tool to do this. > https://github.com/aeris/firewall-piercer > Kind of SOCKS and Transparent proxy over TLS. Thanks

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Ben Tasker
> Is there some way to pass these two options to a remote machine over the TCP channel? Afaik, no. But you could configure the remote machine to transparently proxy and then on your router configure interesting traffic to use that as a gateway - I use Policy Based Routing to direct port 80 traffic

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Aeris
> Is there some way to pass these two options to a remote machine over the > TCP channel? AFAIK, no. > I mean, I could write something like that myself, but maybe > there is a ready made solution? I already dev a tool to do this. https://github.com/aeris/firewall-piercer Kind of SOCKS an

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oskar Wendel : > I mean, I could write something like that myself ... assuming these options can be set with setsockopt from userspace (and preferably without any special privileges), and not only from kernel space. Is this the case? (I'm talking a

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aeris : > Original hostname and port are set by iptables on the socket through > setsockopt, SOL_IP & SO_ORIGINAL_DST, and available on Tor with getsockopt. Thanks. So it would work only locally... Is there some way to pass these two options to a r

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Elrippo : > https://www.elrippoisland.net/public/how_to/anonymity.html Thank you, but it doesn't answer my question. Actually I'm wondering if it is possible to set up the router to pass traffic to the non-local Tor instance. So all iptables rules

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Aeris
> but how can Tor determine the original > destination IP and port that client wanted to reach? How does this magic > work? Hi, Original hostname and port are set by iptables on the socket through setsockopt, SOL_IP & SO_ORIGINAL_DST, and available on Tor with getsockopt. https://gitweb.torproj

Re: [tor-talk] Transparent proxy question

2016-03-07 Thread Elrippo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://www.elrippoisland.net/public/how_to/anonymity.html Am 07. März 2016 23:03:57 MEZ, schrieb Oskar Wendel : >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >Guys, I think I don't understand how exactly transparent proxy in Tor >works. > >Cli

[tor-talk] Transparent proxy question

2016-03-07 Thread Oskar Wendel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guys, I think I don't understand how exactly transparent proxy in Tor works. Client initiates a connection to some IP on some port. This connection is translated on iptables to go to TransProxy IP and port instead. Tor accepts this connection, but