[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2221: allow automatic use of pyOpenSSL 0.14

[Tahoe-LAFS]

#2221: allow automatic use of pyOpenSSL 0.14
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:
         Type:  defect   |     Status:  closed
     Priority:  major    |  Milestone:  1.11.0
    Component:           |    Version:  1.10.0
  packaging              |   Keywords:  packaging setuptools pyopenssl
   Resolution:  fixed    |  cryptography six cffi pycparser
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by warner):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  soon => 1.11.0


Comment:

 We no longer pin the pyOpenSSL version as we used to do, nor do we use
 zetuptoolz. Tahoe now uses the current version of everything.

 We currently have multiple pathways that depend on pyopenssl:

 * a direct dependency that requires `>=0.14`
 * one through `Twisted[tls]` that wants `>=0.13`
 * one through Foolscap that doesn't declare a version
 * one through Foolscap that wants `Twisted[tls]`
 * one through `service-identity` that wants pyopenssl `>=0.12`

 After this release, we'll probably get rid of one on service-identity
 (which is no longer used by twisted; tahoe was depending on it just out of
 paranoia). We might also get rid of the direct dependency, unless there's
 something special about 0.14 that we care about more than Twisted or
 Foolscap.

 But in any event, 0.14 is fine, and in fact modern builds will use the
 current release (which is "16.0.0"). So I'm closing this one out.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2221#comment:24>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage