Deliverable #1 for this summer’s project is this:
“A library for parsing pluggable transport configuration options
This will be a python library that authors of SOCKS proxies can use to
integrate their proxies with Tor.”
A first pass at this is available from github and pypi:
http://github.com/b
> (If this type of mail isn't appropriate for tor-dev please let me
> know...)
It's perfectly appropriate - glad to hear about the improvements!
On a side note, do you think that any txtorcon/stem work would be
appropriate? They're both aiming to be a library that does largely the
same things. Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have tagged txtorcon 0.2, which adds:
. incremental parsing;
. faster TorState startup;
. SAFECOOKIE support;
. several bug fixes;
. options to circuit_failure_rates.py example to make it actually-useful;
. include built documentation + sourc
I have completed the prototype for Torrc and I've tested it writing a
plugin. So far value(), setValue(), TorrcPath() functions are confirmed
working. I've still not been able to get clear() working and the execution
simple stops. I'm not sure if there is an error in the plugin or the
prototype wit
Hi all. As you may have noticed from the elevated traffic on this list
a few of us are trying to do more development discussions in public.
To that end I'm bucking tradition and sending my monthly status report
here too. They've always been public...
http://www.atagar.com/arm/log.php
... but since