Sincerely,
David Stainton
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Dear Aaon Gallagher,
Thanks for the helpful observation. i'm going to make the correction
soon and then we'll be underscore free.
On Wed, Aug 12, 2015 at 7:06 AM, Aaron Gallagher <_...@habnab.it> wrote:
> David Stainton writes:
>
>> If I get rid of this last terrible
I'm not the best person to respond here but I think you should not
want or need to implement your own consumer... Twisted transports and
protocols are implemented using producers and consumers.
On Thu, Sep 3, 2015 at 3:08 AM, Roshan Cherian wrote:
> Hi Team,
>
> I am sorry if this is coming off a
the defense
against certain known active attacks against some mix types.
questions, code review and pull requests welcome.
David Stainton
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
o write various kinds of mixnets,
>> however, we are missing a PKI. Without some kind of public key
>> infrastructure how will mix clients learn about mix public keys?
>>
>> - sphixmixcrypto library needs improvements that would allow us
>> to specify more message types su
Hi,
I'm trying to implement an IWriteDescriptor using raw sockets.
So far this is what I wrote... but it doesn't work:
https://github.com/david415/hushTCP/blob/master/hush_writer.py
Am I doing something obviously wrong here?
I certainly am able to use raw socket + scapy correctly without Twisted
of the
constructor?
On Tue, Oct 1, 2013 at 12:54 AM, Phil Mayers wrote:
> On 10/01/2013 08:30 AM, David Stainton wrote:
>
>>
>> Hi,
>>
>> I'm trying to implement an IWriteDescriptor using raw sockets.
>> So far this is what I wrote... but it doesn't
Oh I was having trouble because my fileno() method was not returning the
correct descriptor. But I fixed it...
Thanks for the excellent suggestion for improving performance!
I've implemented that change. It works great!
On Tue, Oct 1, 2013 at 5:38 AM, wrote:
> On 07:30 am, dstainton...@gmail.
Hi,
I am wondering how I should combine various twisted interfaces
in a way that makes sense. It probably shows here... that I'm new to
twisted.
The Linux iptables can log packets to the netfilter_log which can give
access to user space.
I wrote a simple twisted Reader (IReadDescriptor implementa
pkt)
pkt = self.nflog.send(True)
if pkt is NFWouldBlock: break
My nflog reader seems to work great.
On Wed, Oct 2, 2013 at 12:26 AM, Phil Mayers wrote:
> On 10/02/2013 07:14 AM, David Stainton wrote:
>
>> Hi,
>>
>> I am wondering how I should combine various twi
/documents/12.2.0/core/howto/producers.html
So far I really love Twisted!
On Wed, Oct 2, 2013 at 3:14 AM, Phil Mayers wrote:
> On 02/10/13 09:25, David Stainton wrote:
>
>>
>> In examples of Twisted UDP clients they all do this:
>>
>> reactor.listenUDP(3000,**MyPro
I'm glad I found the doc about producers/consumers... I should actually
finish a transport so I can see this thing churn data.
Thanks for pointing out that decorator.
On Sat, Oct 5, 2013 at 8:46 PM, Glyph wrote:
>
> On Oct 5, 2013, at 10:50 AM, David Stainton
> wrote:
>
>
, David Stainton wrote:
>
> I'm glad I found the doc about producers/consumers... I should actually
> finish a transport so I can see this thing churn data.
> Thanks for pointing out that decorator.
>
>
>
> On Sat, Oct 5, 2013 at 8:46 PM, Glyph wrote:
>
>>
Hi,
I don't know the answer to your question...
I've been thinking about flow control lately.
I recently wrote a little working prototype VPN in Twisted using
IPushProducer and IConsumer interfaces
but I have not yet implemented flow control :
Here we can see how I proxy between TUN and UDP usin
I got my sniffer to work in Twisted... but then I'm not using pycap :
https://github.com/david415/hushVPN/blob/master/nflog_reader.py
I use the NetLinkFilter socket via this python cffi:
https://github.com/mk-fg/scapy-nflog-capture
Anyhow this allows me to control which packets my sniffer picks up
Hi, I'd like to help out and write unit tests for the Socks v5 code in
this ticket:
https://twistedmatrix.com/trac/ticket/1330
Should I write something very similar to this?? ::
http://twistedmatrix.com/trac/browser/trunk/twisted/test/test_socks.py
My goal is getting socksv5 client and server cod
Hi Jean-Paul,
Thanks for all the info, observations about the existing code and for
the coding advice!
I think I should only implement the socks 5 server side
since txsocksx seems to have the client implementation covered.
Some of the Tor developers use it...
I'm not used to test driven developm
ens.NegotiationError: no connection established within
client timeout
foolscap.test.test_appserver.RunCommand.test_run
---
Ran 1 tests in 60.576s
FAILED (errors=1)
foolscap$
Ch
Thanks! That's just what I needed.
On Sat, Mar 8, 2014 at 12:52 PM, wrote:
> On 10:02 am, dstainton...@gmail.com wrote:
>>
>>
>>
>> Greetings,
>>
>> My goal is to get Brian Warner's foolscap library ported to Twisted
>> endpoints instead of the older Twisted api interfaces it currently
>> uses (
Greetings,
I wrote a simple IStreamClientEndpointStringParser for using the
SOCKS5ClientEndpoint with Tor:
https://gist.github.com/david415/26a4ed59078d2e27376f
I modified a txsocksx code example for testing the new endpoint descriptor:
https://gist.github.com/david415/7c6040117319cc3b0230
...bu
Hi Jean-Paul,
Thanks for the suggestions.
OK... here's my SSCCE:
cd projects/virtualenv-1.11.1/
./virtualenv.py ~/virtenv-endpoints-test
. ~/virtenv-endpoints-test/bin/activate
usewithtor pip install twisted
cd ~/projects
git clone https://github.com/david415/txsocksx.git
cd txsocksx
git checkout
ah ok... i made it work. Thanks!
On Wed, Apr 30, 2014 at 5:00 PM, wrote:
> On 03:50 pm, dstainton...@gmail.com wrote:
>>
>> Hi Jean-Paul,
>>
>> Thanks for the suggestions.
>> OK... here's my SSCCE:
>
>
> It looks like you need to make an instance of
> `TorClientEndpointStringParser`. If a class
Greetings,
Today I wrote an endpoint parser for Meejah's txtorcon Tor Hidden
Service endpoint.
Now that we have foolscap ported to twisted endpoints (branch needs
review but I should probably rebase first) we'd like to be able to
simply specify an "onion" endpoint descriptor in Tahoe-LAFS
configu
descriptors from the user and
passes them to foolscap.
On Fri, May 2, 2014 at 2:20 PM, Tristan Seligmann
wrote:
> 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
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
>> 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?
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
ch this
soon. For now my hacky development/testing flow works OK.
On Fri, May 2, 2014 at 9:18 PM, Glyph Lefkowitz wrote:
>
> 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 i
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
> 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
Hi Jay Shah,
I started (but never finished) to implement a tcp traceroute (with
interesting features) for OONI (Open Observatory of Network
Interference... a Tor Project project) probe. You might use parts of
the ooniprobe api to capture your packets... It's written using
Twisted and I'm fairly ce
It seems like a fairly common idiom to setup some sort of TCP server
with a kernel selected port
via an endpoint descriptor like this:
def getListeningPort(listeningPort):
address = listeningPort.getHost()
endpointDesc = convertAddressToEndpointDesc(address)
sendAnnouncement(endpointDe
Greetings,
I was inspired by the "socat" CLI utility to write something similar called
twistedcat.
https://github.com/david415/twistedcat
https://github.com/david415/twistedcat/blob/master/twistedcat/twistedcat.py
Obviously it should have the "cat" word in the name... so what do you suggest?
Greetings,
I wanted to see what people think of this before attempting to open a
Twisted trac ticket and submitting code patches.
I think Twisted servers need a way to derive a client endpoint
descriptor string from a listeningPort. This approximates an idiom
commonly used in Tahoe-LAFS/Foolsca
34 matches
Mail list logo
