[Twisted-Python] txtorcon 0.14.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm happy to announce txtorcon 0.14.0. Changes:
* IStreamAttacher handling was missing None and DO_NOT_ATTACH cases if a Deferred was returned.
* add .is_built Deferred to txtorcon.Circuit that gets callback()'d when the circuit becomes BUILT
* David Stainton ported his "tor:" endpoint parser so now both client
and server endpoints are supported. This means **any** Twisted
program using endpoints can use Tor as a client. For example, to
connect to txtorcon's Web site: ep =
clientFromString("tor:timaq4ygg2iegci7.onion:80"). (In the future,
I'd like to automatically launch Tor if required, too).
* Python3 fixes from Isis Lovecruft (note: needs Twisted 15.4.0+)
You can download the release from PyPI or GitHub (or of course "pip
install txtorcon"):
https://pypi.python.org/pypi/txtorcon/0.14.0
https://github.com/meejah/txtorcon/releases/tag/v0.14.0
Releases are also available from the hidden service:
http://timaq4ygg2iegci7.onion/txtorcon-0.14.0.tar.gz
http://timaq4ygg2iegci7.onion/txtorcon-0.14.0.tar.gz.asc
http://timaq4ygg2iegci7.onion/txtorcon-0.14.0-py2-none-any.whl
http://timaq4ygg2iegci7.onion/txtorcon-0.14.0-py2-none-any.whl.asc
You can verify the sha256sum of both by running the following 4 lines
in a shell wherever you have the files downloaded:
cat <
On Sep 26, 2015, at 11:26 PM, meejah
wrote: * David Stainton ported his "tor:" endpoint parser so now both client and server endpoints are supported. This means **any** Twisted program using endpoints can use Tor as a client. For example, to connect to txtorcon's Web site: ep = clientFromString("tor:timaq4ygg2iegci7.onion:80"). (In the future, I'd like to automatically launch Tor if required, too).
Hooray! Once again, txtorcon blazes the trail in making use of Twisted's extensibility :-). Thanks for setting this example! Could you use any help auto-launching Tor? -glyph
Glyph Lefkowitz
Could you use any help auto-launching Tor?
This would actually be a fairly straightforward bit of refactoring, mostly -- the "server-side" endpoints ("onion:...") already do auto-launch Tor, and there are some @staticmethods to directly create TCPHiddenServiceEndpoints attached to existing or launched Tor instances. If anyone would like to help, that'd be great; the enhancement ticket for the "tor:..." endpoints is: https://github.com/meejah/txtorcon/issues/128 Anything unclear can be discussed there. Note that currently the usual strategy for "onion:" endpoints is to launch a new Tor instance because of permissions "reasons" -- for the "tor:" type endpoints, any running Tor that has a valid SOCKS port should work, so that should be the preferred strategy *unless* .get_global_tor() has ever been called, in which case that Tor instance should be used. I'm usually idling in #tor-dev on OFTC if anyone wants to take a try at this :) Thanks! meejah
meejah
* add .is_built Deferred to txtorcon.Circuit that gets callback()'d when the circuit becomes BUILT
This had a bug in it. I give you 0.14.1:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There was a subtle bug with the Circuit.is_built API introduced in
0.14.0, necessitating this release.
I've also changed the API (with backwards-compatibility for now) to a
method-call that returns a Deferred: Circuit.when_built()
You can download the release from PyPI or GitHub (or of course "pip
install txtorcon"):
https://pypi.python.org/pypi/txtorcon/0.14.1
https://github.com/meejah/txtorcon/releases/tag/v0.14.1
Releases are also available from the hidden service:
http://timaq4ygg2iegci7.onion/txtorcon-0.14.1.tar.gz
http://timaq4ygg2iegci7.onion/txtorcon-0.14.1.tar.gz.asc
http://timaq4ygg2iegci7.onion/txtorcon-0.14.1-py2-none-any.whl
http://timaq4ygg2iegci7.onion/txtorcon-0.14.1-py2-none-any.whl.asc
You can verify the sha256sum of both by running the following 4 lines
in a shell wherever you have the files downloaded:
cat <
participants (2)
-
Glyph Lefkowitz
-
meejah