Yawning Angel yawn...@schwanenlied.me wrote:
On Mon, 17 Feb 2014 19:34:36 +
Yawning Angel yawn...@schwanenlied.me wrote:
I will address the GCC build issues when I'm done working on that.
The system gcc on 9.1p10 is ancient (4.2.1), and does not support
C++11, so I would have to
On Wed, Feb 12, 2014 at 08:53:53PM -0500, Utsarga Sikder wrote:
If you guys want to set up a meeting time, fill this out. If you want to see
the results, go here - http://whenisgood.net/nhhy5yt/results/gqtpzak
Looks like Feb. 22nd at 15:00 UTC is fine for us all. Let's meet in #tor-dev
on
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 there.
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 to
On Wed, 19 Feb 2014 13:52:01 +0100
Fabian Keil freebsd-lis...@fabiankeil.de wrote:
It also builds on 9.2 and 8.4 now:
https://redports.org/buildarchive/20140218142926-87456/
(The failures on EXP1 and QATty are unrelated)
Looks like the tests are SIGSEGVing on 9.2/8.4, I replicated the
issue,
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 there.
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 (pyptlib), SOCKS,
