Mailman 3 March 2005 - Twisted

[Twisted-Python] Need SSH help
by Bad_Bob March 2, 2005

March 2, 2005

I am trying to write an encrypted P2P program (cryptic6.sourceforge.net). I am trying to understand twisted's ssh. Thanks to the helpful people on #twisted I have am able to get the twisted client to send messages to the twisted server. This works when I use the keys provided in the example. However when I try to generate my own keys it always complains that they are not password. This is the code I am using to generate public/private key pairs: twisted.scripts.ckeygen.generateRSAkey({'bits':1048,'filename': os.path.join(os.path.expanduser('~'),'.cryptic6/keys'),'pass':pass) This is the error I get: 2005/03/02 14:37 UTC [-] Log opened. 2005/03/02 14:37 UTC [-] Traceback (most recent call last): 2005/03/02 14:37 UTC [-] File "sshsimpleserver.py", line 97, in ? 2005/03/02 14:37 UTC [-] class ExampleFactory(factory.SSHFactory): 2005/03/02 14:37 UTC [-] File "sshsimpleserver.py", line 101, in ExampleFactory 2005/03/02 14:37 UTC [-] privateKeys = { 2005/03/02 14:37 UTC [-] File "/usr/lib/python2.3/site-packages/twisted/conch/ssh/keys.py", line 180, in getPrivateKeyObject 2005/03/02 14:37 UTC [-] return getPrivateKeyObject_openssh(data, passphrase) 2005/03/02 14:37 UTC [-] File "/usr/lib/python2.3/site-packages/twisted/conch/ssh/keys.py", line 207, in getPrivateKeyObject_openssh 2005/03/02 14:37 UTC [-] raise BadKeyError, 'encrypted key with no passphrase' 2005/03/02 14:37 UTC [-] twisted.conch.ssh.keys.BadKeyError: encrypted key with no passphrase Is there another way I should generate the keys? Thanks

2 3

[Twisted-Python] Re: Patch to support DNS updates
by Jeff Silver March 1, 2005

March 1, 2005

> Size of python data types is pretty irrelevant when DNS SOA serial > number is an unsigned 32-bit number. January 1st, 2043 would be > > 4301010000 > YYMMDDHHMM > > which is > 2**32, and thus invalid. Ahhh! I see. Thanks. I'll do something different. > This is all pretty academical, of course. It's just that you've created > a totally new _class_ of y2k-like bugs, with your > YYYYMMDDHHMM - 200000000000 scheme, and I think that's worth some kind > of a prize. How kind! Maybe that balances out the one real y2k bug I fixed in 1999. I'm still looking forward to the year 2008 bug that no-one seems to be worried about (2-digit year read by a program/language that treats leading zero as an octal indicator - and yes, I have seen an example). Thanks again for your comments.

1 0

[Twisted-Python] linux kernel 2.6.11-rc broke twisted process pipes
by Andrea Arcangeli Feb. 28, 2005

Feb. 28, 2005

Hello everyone, Please read the attached emails. I would like to understand exactly what broke twisted, so that we're sure the new 2.6.11 kernel will work reliably with twisted. This code especially will never trigger with 2.6.11 because we'll never set POLLIN|POLLOUT at the same time for writeable fd. def doRead(self): """The only way this pipe can become readable is at EOF, because the child has closed it. """ fd = self.fd r, w, x = select.select([fd], [fd], [], 0) if r and w: return CONNECTION_LOST Could you answer why anybody should call doRead on a writeable fd? Where is it written that at EOF a _write_ pipe channel becomes readable? Is it ok that "r and w" will never trigger at the same time anymore, right? Was just that a superflous assumptions? Note that with 2.6.8 and all previous linux kernels, "r and w" could be == True in normal conditions too if the pipe write buffer was empty (old kernel was setting pollin always for no good reason). What I suspect is that the above is a superflous check that was working by luck with older kernels (becasue we could set in and out at the same time even without a disconnect event), and that all you care about is to get the wakeup from the write or disconnect events. And in turn the new linux 2.6.11-rc should not work by luck anymore. Comments appreciated. Thanks.

3 8