txtorcon icon indicating copy to clipboard operation
txtorcon copied to clipboard

Twisted-based asynchronous Tor control protocol implementation. Includes unit-tests, examples, state-tracking code and configuration abstraction.

Results 49 txtorcon issues
Sort by recently updated
recently updated
newest added

Since 0.19.0 `get_info` commands will return unicode values instead of strings. It could be that other people would also be a bit surprised by this fact, so at the very...

documentation

This has bandwidth, unmeasured maybe other things.

enhancement

In the FreeBSD port we only need to install docs and examples when corresponding port options are chosen. Currently, we have to patch setup.py to achieve this. It would have...

enhancement
needs-investigation

As found by @aagbsn and @DonnchaC from bwscanner work, if you change `UseMicrodescriptors` the list of routers will be empty until a NEWCONSENSUS event arrives. `TorConfig` should probably snoop for...

enhancement
documentation
needs-investigation

It might be useful to have a convenience method for "wait for a single event of X". (e.g. bwscanner wants/needs to wait for a NEWCONSENSUS event after changing the config...

enhancement

If Tor is dormant and txtorcon connects and tries to build a circuit, this may fail with `552 no descriptor for X` because Tor still fetches enough consensus to know...

enhancement

Some applications want to set up endpoints (e.g. for Onion services or client connections) before doing any "async stuff". This means they can't yet have a `Tor` instance, because that...

enhancement
needs-review

I'm updating magic-wormhole to use the new txtorcon APIs, and I noticed one difference between the `_is_non_public_numeric_address()` function in txtorcon and the one in magic-wormhole that inspired it. The magic-wormhole...

Our notion of the current list of guard nodes will become out of sync unless we use the `GUARD` event to notice guards going up and down.

bug
easy_ticket

atagar tells me in #tor-dev that "contact" and "platform" in descriptors can take arbitrary bytes. Everything else from tor-control is ASCII. But those two special cases _can_ leak through if...

question