Merge lp:~exarkun/pyopenssl/tlsv1_1or2 into lp:~exarkun/pyopenssl/trunk
Proposed by
Jean-Paul Calderone
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 171 | ||||
Proposed branch: | lp:~exarkun/pyopenssl/tlsv1_1or2 | ||||
Merge into: | lp:~exarkun/pyopenssl/trunk | ||||
Diff against target: |
275 lines (+109/-29) 5 files modified
OpenSSL/ssl/context.c (+29/-5) OpenSSL/ssl/context.h (+2/-0) OpenSSL/ssl/ssl.c (+8/-0) OpenSSL/test/test_ssl.py (+24/-11) doc/api/ssl.rst (+46/-13) |
||||
To merge this branch: | bzr merge lp:~exarkun/pyopenssl/tlsv1_1or2 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jean-Paul Calderone | Pending | ||
Review via email:
|
Description of the change
Introduces conditional support for TLSv1.1 and TLSv1.2 (conditional on whether the wrapped version of OpenSSL supports them).
To post a comment you must log in.
I don't understand this code very well, but this looks suspicious:
18 +#ifdef SSL_OP_NO_TLSv1_1
19 +#define TLSv1_2_METHOD_TEXT " TLSv1_2_METHOD"
20 +#endif
Shouldn't it be SSL_OP_NO_TLSv1_2 instead? And if so, and this is a bug, does this mean there isn't an automated test that tries to build pyOpenSSL against some version of OpenSSL that has or doesn't have the #defines necessary to trigger this bug?