We technically don't need to use a tun device for the dns transport... but if a
tun device is used for the tor dns transport then we get the reliability layer
without having to write it ourselves. It doesn't matter that tun devices are
lossy and udp is unreliable; we just spray packets.
Obfspro
Hello David and George and other people who are interested in there being even
more obfuscation transports for tor, I appreciate the thought of making a
frankenstein butchering of obfsproxy code which transports tor over dns... and
speaks socks and tor control port... and works to PT spec... bu
I was thinking that a generalized mechanism for using vpns as
obfsproxy transports would help solve for a dns transport... since a
dns transport is going to use a tun device. Perhaps
obfsproxy/network/launch_transport.py can be changed so that it has a
vpn role... where it sets up the tun device an
On Wed, Feb 19, 2014 at 04:59:05PM -0800, George Kadianakis wrote:
> > George Kadianakis:
> >> b) You can write your own Python code and selectively steal code from
> >>obfsproxy. You will have to steal the code that does networking,
> >>Extended ORPort, environment variable parsing (pyptli
On Wed, Feb 19, 2014 at 05:00:09PM -0800, George Kadianakis wrote:
> FWIW, people told me that Freenet has had a DNS transport for ages.
> There is also this:
> https://lists.torproject.org/pipermail/tor-talk/2006-January/007124.html
We had a little bit of brainstorming on a DNS transport on the
P
>>
>>
>> George,
>>
>> I'd like to write a dns transport... and it seems to me the
>> obfsproxy api isn't designed for non tcp transports...
>> Maybe we again make some changes to the obfsproxy api?
>> It would transport IP packets using a tun device...
>> we can route it to a socks endpoint and pr
> George Kadianakis:
>> b) You can write your own Python code and selectively steal code from
>>obfsproxy. You will have to steal the code that does networking,
>>Extended ORPort, environment variable parsing (pyptlib), SOCKS,
>>etc. This might not be too hard.
>
> Could the shared code
George Kadianakis:
> b) You can write your own Python code and selectively steal code from
>obfsproxy. You will have to steal the code that does networking,
>Extended ORPort, environment variable parsing (pyptlib), SOCKS,
>etc. This might not be too hard.
Could the shared code be used
>
>
> George,
>
> I'd like to write a dns transport... and it seems to me the
> obfsproxy api isn't designed for non tcp transports...
> Maybe we again make some changes to the obfsproxy api?
> It would transport IP packets using a tun device...
> we can route it to a socks endpoint and proxy from
