From dave at immunitysec.com Wed Jul 10 02:08:56 2002 From: dave at immunitysec.com (Dave Aitel) Date: 09 Jul 2002 20:08:56 -0400 Subject: [pyOpenSSL] .5 release Message-ID: <1026259736.3286.44.camel@localhost.localdomain> Just out of curiosity...when is .5 scheduled for release? -dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part URL: From martin at strakt.com Wed Jul 10 10:24:57 2002 From: martin at strakt.com (Martin =?ISO-8859-1?Q?Sj=F6gren?=) Date: 10 Jul 2002 10:24:57 +0200 Subject: [pyOpenSSL] .5 release In-Reply-To: <1026259736.3286.44.camel@localhost.localdomain> References: <1026259736.3286.44.camel@localhost.localdomain> Message-ID: <1026289497.6397.34.camel@ratthing-b3cf> ons 2002-07-10 klockan 02.08 skrev Dave Aitel: > Just out of curiosity...when is .5 scheduled for release? It's not scheduled :( but I sure hope to get it released before the end of July... I've added some new features that got contributed by people (X509 extensions, PKCS7...), general cleanup and a load of bug fixes. So, somewhere within the next three weeks is as exact as it is right now. Sorry I can't do better than that :( Regards, Martin -- Martin Sj?gren martin at strakt.com ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html From dave at immunitysec.com Wed Jul 10 11:19:35 2002 From: dave at immunitysec.com (Dave Aitel) Date: 10 Jul 2002 05:19:35 -0400 Subject: [pyOpenSSL] .5 release In-Reply-To: <1026289497.6397.34.camel@ratthing-b3cf> References: <1026259736.3286.44.camel@localhost.localdomain> <1026289497.6397.34.camel@ratthing-b3cf> Message-ID: <1026292775.5312.49.camel@localhost.localdomain> Nuts. I wanted to release spkproxy.py this week some time. :< Would it be ok if I also distroed with it the pre5.tar.gz? I really need set_accept_state() to work. Also, since you already have a client.py, you might as well distro the spkproxy.py, if you want. I'm going to be including it with SPIKE (www.immunitysec.com/spike.html), which is GPL. But it seems like a natural fit for client.py...:> For what it's worth, I haven't had any problems with my pre5. :> -dave On Wed, 2002-07-10 at 04:24, Martin Sj?gren wrote: > ons 2002-07-10 klockan 02.08 skrev Dave Aitel: > > Just out of curiosity...when is .5 scheduled for release? > > It's not scheduled :( but I sure hope to get it released before the end > of July... I've added some new features that got contributed by people > (X509 extensions, PKCS7...), general cleanup and a load of bug fixes. > > So, somewhere within the next three weeks is as exact as it is right > now. Sorry I can't do better than that :( > > > Regards, > Martin > > -- > Martin Sj?gren > martin at strakt.com ICQ : 41245059 > Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 > GPG key: http://www.strakt.com/~martin/gpg.html > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Two, two, TWO treats in one. > http://thinkgeek.com/sf > _______________________________________________ > pyopenssl-list mailing list > pyopenssl-list at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pyopenssl-list > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part URL: From martin at strakt.com Wed Jul 10 11:14:08 2002 From: martin at strakt.com (Martin =?ISO-8859-1?Q?Sj=F6gren?=) Date: 10 Jul 2002 11:14:08 +0200 Subject: [pyOpenSSL] .5 release In-Reply-To: <1026292775.5312.49.camel@localhost.localdomain> References: <1026259736.3286.44.camel@localhost.localdomain> <1026289497.6397.34.camel@ratthing-b3cf> <1026292775.5312.49.camel@localhost.localdomain> Message-ID: <1026292448.15178.1.camel@ratthing-b3cf> ons 2002-07-10 klockan 11.19 skrev Dave Aitel: > Nuts. I wanted to release spkproxy.py this week some time. :< Would it > be ok if I also distroed with it the pre5.tar.gz? I really need > set_accept_state() to work. Sure. > Also, since you already have a client.py, you might as well distro the > spkproxy.py, if you want. I'm going to be including it with SPIKE > (www.immunitysec.com/spike.html), which is GPL. But it seems like a > natural fit for client.py...:> Cool, more example code is always good :-) > For what it's worth, I haven't had any problems with my pre5. :> Well, I have, but I've fixed those ;) Regards, Martin -- Martin Sj?gren martin at strakt.com ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html From eric.johnson at flypanam.com Fri Jul 26 16:02:43 2002 From: eric.johnson at flypanam.com (Eric Johnson) Date: Fri, 26 Jul 2002 10:02:43 -0400 Subject: [pyOpenSSL] FTPS client Message-ID: <20020726140243.GA4588@flypanam.com> Hello, I need an FTPS client that will work against the WS_FTP Server from Ipswitch (http://www.ipswitch.com/Products/WS_FTP-Server/index.html) It appears that I might be able to use one included with the M2Crypto module, but I'd rather see if I can get one (or write my own) with pyOpenSSL. I like it's design goal better that M2Crypto AND there are Debian packages for it! Does anyone know if a pyOpenSSL FTPS client exists, or have any pointers on how to get started writing my own? Thanks in advance, Eric -- // Eric Johnson (eric.johnson at flypanam.com || 603.766.2216) // Public Key: http://wwwkeys.us.pgp.net/ 0x634BB5E3 // // Anything cut to length will be too short. // // gpg (GnuPG) 1.0.6 - Copyright (C) 2001 Free Software Foundation, Inc. // Key fingerprint = CC0B 75C4 CC01 AC82 D24E BEE8 A4C0 06E9 634B B5E3 From twisted at itamarst.org Fri Jul 26 17:04:59 2002 From: twisted at itamarst.org (Itamar Shtull-Trauring) Date: Fri, 26 Jul 2002 11:04:59 -0400 Subject: [pyOpenSSL] FTPS client References: <20020726140243.GA4588@flypanam.com> Message-ID: <3D41651B.5060506@itamarst.org> Eric Johnson wrote: > Does anyone know if a pyOpenSSL FTPS client exists, or have > any pointers on how to get started writing my own? Writing your own shouln't be hard - you'll need pyOpenSSL 0.5 or CVS though. The main thing that makes FTL/TLS difference is, I think, that when the server connects back to the client, the client is the one that initializes TLS, not the server, so you need to separate out TLS connect from TCP connect. Reading M2Crypto version should show you how to do it in any case.