Griffin Boyce:
> Hello all,
>
> So I'm part of a team working on wireless mesh, and Torouter has come up
> a few times this week. Is it actively being developed? Given the state of
> the roadmap [1], I'd sort of assumed it was inactive or on hiatus, but
> others had heard differently.
>
Yes,
adrelanos wrote:
> Accesslabs: no visible progress. No saying there is none or they are not
> working on it, but I never found a public mailing list, git repository,
> trac timeline is empty. Happy to be proven wrong. Perhaps mail them.
>
I haven't heard of any substantial movement on torouter
Griffin Boyce:
> Hello all,
>
> So I'm part of a team working on wireless mesh, and Torouter has come up
> a few times this week. Is it actively being developed? Given the state of
> the roadmap [1], I'd sort of assumed it was inactive or on hiatus, but
> others had heard differently.
>
> tha
Hello all,
So I'm part of a team working on wireless mesh, and Torouter has come up
a few times this week. Is it actively being developed? Given the state of
the roadmap [1], I'd sort of assumed it was inactive or on hiatus, but
others had heard differently.
thanks,
Griffin Boyce
--
Technic
Karsten, could I ask you to take a quick look at this code?
https://trac.torproject.org/projects/tor/ticket/7549#comment:14
https://trac.torproject.org/projects/tor/attachment/ticket/7549/onionoo-querying-ver2.zip
It's a daemon that keeps a local cache of potential exit relays, sourced
from onion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
txtorcon 0.8.0 is now tagged and released. [1]
txtorcon is a Python+Twisted-based asynchronous implementation of the
Tor control protocol. It includes a state-tracking abstraction,
configuration abstraction, Twisted endpoint support for hidden
servi
