On 06:59 am, mee...@meejah.ca wrote:
[snip]
Anyway, one really cool thing now that txtorcon supports endpoints is
that you can install it, and then easily make Twisted Web serve some
content as a hidden service (launching a Tor instance first, etc):
twistd -n web --port "onion:80" --path ~/p
As a followup to all this, I have just merged a branch with a refactored
endpoint parser. tomprince (I believe) on #twisted suggested some SSH
endpoint code to look at, which inspired the @classmethod style way of
getting a TCPHiddenServiceEndpoint instance configured differently.
Nearly all the
On May 6, 2014, at 4:38 AM, David Stainton wrote:
> However I was thinking that the "only_tor" mode for tahoe (mentioned
> here https://tahoe-lafs.org/trac/tahoe-lafs/ticket/517#comment:15 )
> could be implemented in tahoe... it could filter endpoint descriptors
> by calling clientFromString or s
> The endpoint constructor should do _construction_. The endpoint parser
> should do _parsing_. The task of parsing is of taking strings and producing
> meaningful values.
Ah yeah I see what you mean. OK... I changed it:
https://github.com/david415/txtorcon/commit/1e96d550c40bef1be1b45c3c975c0da
On May 5, 2014, at 6:52 PM, David Stainton wrote:
> OK... I decided that txtorcon's endpoint constructor should only take
> string arguments besides the reactor arg...
> because serverFromString passes only str args to the endpoint constructor.
I strongly suggest that this is wrong.
The endpoi
OK... I decided that txtorcon's endpoint constructor should only take
string arguments besides the reactor arg...
because serverFromString passes only str args to the endpoint constructor.
I wrote the endpoint parser to be as simple as possible.
The endpoint's `listen` method now handles the tor c
On May 2, 2014, at 5:45 PM, David Stainton wrote:
> I'm starting to think about the deployment issues... Perhaps someone
> on the list knows of the "correct" setup.py (distutils/setuputils?)
> procedure to deploy twisted plugins? I shall have to research this
> soon. For now my hacky development/
Thanks. Sure thing. Yes I have every intention of contributing
endpoint parsers to txtorcon and txsocksx for use with tor.
Both of these could make it much easier for developers to make their
applications tor friendly.
The endpoints/endpoint parsers api is brilliant! When the tor
client/server end
Ah yeah... twisted endpoints that support udp...
Perhaps when Yawning Angel finishes Lightweight Obfuscated Datagram
Protocol (LODP) there will be interesting things we can do with
this... and a more immediate perceived need for twisted datagram
endpoint interfaces.
On Fri, May 2, 2014 at 9:16 PM
>> Ah ha! Of course it is so obvious now that you point it out to me.
>> The onion endpoint parser can do this setup work in it's `listen`
>> method which returns a `Deferred`.
>> Thanks for your observation/advice!
>
> Cool! Thanks for doing this. Can I pull it into txtorcon when it's
> finished?
On May 2, 2014, at 6:59 AM, David Stainton wrote:
> Today I wrote an endpoint parser for Meejah's txtorcon Tor Hidden
> Service endpoint.
This is fantastic. Basically this is _exactly_ the use-case that we had in
mind when designing the endpoint parser plugin APIs.
Thanks so much for doing i
On May 2, 2014, at 1:02 PM, meejah wrote:
> Another point for this is that "someday" tor will have UDP support...
There's a reason that the existing interfaces all have "stream" in their names
:-).
The main reason we didn't do "datagram" at the same time is that there's a
pretty clear client/
David Stainton writes:
> Ah ha! Of course it is so obvious now that you point it out to me.
> The onion endpoint parser can do this setup work in it's `listen`
> method which returns a `Deferred`.
> Thanks for your observation/advice!
Cool! Thanks for doing this. Can I pull it into txtorcon whe
Ah ha! Of course it is so obvious now that you point it out to me.
The onion endpoint parser can do this setup work in it's `listen`
method which returns a `Deferred`.
Thanks for your observation/advice!
Cheers!
David
On Fri, May 2, 2014 at 3:01 PM, wrote:
> On 02:53 pm, dstainton...@gmail.co
On 02:53 pm, dstainton...@gmail.com wrote:
I get what you are saying... but let's back up a second;
foolscap (in my branch
https://github.com/david415/foolscap/tree/endpoint_descriptors_server2)
uses clientFromString and serverFromString to translate twisted
endpoint descriptors into endpoint obj
I get what you are saying... but let's back up a second;
foolscap (in my branch
https://github.com/david415/foolscap/tree/endpoint_descriptors_server2)
uses clientFromString and serverFromString to translate twisted
endpoint descriptors into endpoint objects... AND foolscap
doesn't know any details
On 2 May 2014 15:59, David Stainton wrote:
> This will work fine for the txsocksx tor client endpoint parser I
> wrote... However the txtorcon Tor Hidden Service endpoint setup
> requires a deferred to fire once the tor process is started... This
> means that the endpoint parser needs to return a
17 matches
Mail list logo
