Changes between Version 2 and Version 4 of Ticket #2221


Ignore:
Timestamp:
2014-10-17T11:15:17Z (10 years ago)
Author:
daira
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2221 – Description

    v2 v4  
    1 For Tahoe-LAFS 1.11 we decided to fix the pyOpenSSL version requirement to == 0.13, in order to mitigate problems with building the `cryptography` library that is a dependency of pyOpenSSL >= 0.14 (see #2193 for details).
     1For 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).
    22
    3 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 non-Windows platforms).
     3This 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).