Opened at 2014-04-14T23:02:16Z

Last modified at 2016-03-28T04:04:33Z

#2221 closed defect

allow use of pyOpenSSL 0.14 — at Version 4

Reported by: daira Owned by:
Priority: major Milestone: 1.11.0
Component: packaging Version: 1.10.0
Keywords: packaging setuptools pyopenssl cryptography six cffi pycparser Cc: vladimir@…
Launchpad Bug:

Description (last modified by daira)

For Tahoe-LAFS 1.11 we decided to fix the pyOpenSSL version requirement to == 0.13 [not quite; see comment:4 below], in order to mitigate problems with building the cryptography library that is a dependency of pyOpenSSL >= 0.14 (see #2193 for details).

This ticket is for a longer-term solution to allow use of pyOpenSSL >= 0.14 without causing build/install regressions (such as #2217, or the requirement to manually install libffi on some platforms).

Change History (4)

comment:1 Changed at 2014-04-15T01:12:50Z by daira

  • Description modified (diff)

comment:2 Changed at 2014-04-15T01:13:47Z by daira

  • Description modified (diff)

comment:3 Changed at 2014-05-12T21:42:37Z by glyph

For what it's worth, you don't need to manually install libffi on the mac, at least; it's bundled with the platform.

comment:4 Changed at 2014-10-17T11:15:17Z by daira

  • Description modified (diff)

The solution we eventually arrived at for 1.11 (for all platforms) was to attempt to import the OpenSSL module at build time and check its version; if 0.14 or above is already installed then we allow it, otherwise we use 0.13 or 0.13.1.

This is not entirely satisfactory; it's complicated and means that we don't get pyOpenSSL security fixes unless 0.14+ is installed manually.

Note: See TracTickets for help on using tickets.