Opened 12 years ago

Closed 10 years ago

#1121 enhancement closed duplicate (duplicate)

Twisted fork of pyOpenSSL (pyTLS ?)

Reported by: landonf Owned by: landonf
Priority: lowest Milestone:
Component: core Keywords:
Cc: Glyph, radix, itamarst, jknight, titty, landonf, Jean-Paul Calderone Branch:
Author:

Description


Attachments (1)

mycrypto.tgz (4.0 KB) - added by titty 12 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 12 years ago by landonf

This is a proposal for the creation of a Twisted fork of pyOpenSSL, maintained
by myself.

I am well aquanted with OpenSSL, and the author of Bacula's TLS implementation:
http://cvs.sourceforge.net/viewcvs.py/bacula/bacula/src/lib/tls.c?rev=1.4&view=markup

comment:2 Changed 12 years ago by Glyph

I've reviewed the code referred to here, and various comments made on IRC and
I'm relatively impressed.  Normally at this point I'd wait for patches before
suggesting commit access, but I don't care to review a patch that contains the
entirety of PyOpenSSL.

This should probably refer to #778

landonf: I'm assuming that you're legally able to consign copyright or to
provide code to us under the MIT license.  Please make sure with your employer...

radix: (or anyone with pyramid privileges) please create an account on wolfwood

This work should initially happen in an SVN branch, not on trunk.

comment:3 Changed 12 years ago by itamarst

Note that PyOpenSSL is licensed under "LGPL plus exemption for OpenSSL
advertisement clause."

comment:4 Changed 12 years ago by itamarst

Do we want this to be twisted.something or a separate package? If it's a
separate package we will get help from other frustrated pyOpenSSL users, and due
to that and licensing separate package seems the way to go (PyTLS sounds good).

Note that Laura Creighton claims that Strakt is maintaining PyOpenSSL; I eamiled
her indicating we have pending patches and await response.

comment:5 Changed 12 years ago by jknight

I'd just like to add that I'm quite happy to see someone both competent and 
willing to take on this project. I've been irritated by the state of pyOpenSSL 
for a while now, especially with regards to some changes that twisted could 
really use.

However, I've not had the energy to actually do anything like take over 
maintainership myself. So it's great that you want to do so. :)

Changed 12 years ago by titty

Attachment: mycrypto.tgz added

comment:6 Changed 12 years ago by titty

Is there any work being done on this one?
I'm attaching some pyrex code, which wraps PKey objects. It should be relatively
easy to integrate this with pyOpenSSL.

comment:7 Changed 12 years ago by radix

Ok, I *finally* gave Landon a wolfwood account. Back to you.

comment:8 Changed 11 years ago by Jean-Paul Calderone

Cc: Jean-Paul Calderone added
Component: conch

So uh, how's this going?

What's the state of the openssl-1121 branch in the repository?

comment:9 Changed 11 years ago by Jean-Paul Calderone

Landon conveyed to me on IRC that he is unlikely to do much more work on this.

comment:10 Changed 11 years ago by Glyph

Component: conchcore
Priority: normallowest

He indicated similarly to me. I don't want to close this because maybe someone else will take it over one day, but I am lowering the priority becuase I don't think it's actually a pressing issue unless someone wants to work on it.

comment:11 Changed 10 years ago by Jean-Paul Calderone

Resolution: duplicate
Status: newclosed

Closing this in favor of #2293.

This is not so much a fork as the resumption of maintenance duties by a different party.

;)

Note: See TracTickets for help on using tickets.