Opened at 2007-04-27T04:47:31Z
Last modified at 2008-10-31T15:33:21Z
#11 closed defect
I don't like pyopenssl — at Initial Version
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | code | Version: | 0.6.1 |
| Keywords: | Cc: | heikki | |
| Launchpad Bug: |
Description
There is no known way (to me) way to get pyopenssl running on Windows without finding a binary that somebody has uploaded somewhere (i.e., not an actual supported package on an official project's web site or anything). For example, right now the best way for our Windows users to get pyOpenSSL is to get this binary:
http://allmydata.org/source/pyOpenSSL-0.6.win32-py2.5
Which I copied from webcleaner.sf.net.
I wouldn't know how to rebuild this if we needed to, for example if someone discovered a critical security hole in it.
Also, pyopenssl's web site hasn't been updated since 2004.
Also, it apparently uses lots of memory for secure connections, although Brian might want to add more accurate and precise notes about that issue.
All in all, I would be really happy to find a well maintained, easy to compile alternative.
