aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Kehrer <paul.l.kehrer@gmail.com>2013-12-25 18:06:42 -0600
committerPaul Kehrer <paul.l.kehrer@gmail.com>2013-12-25 18:06:42 -0600
commit5f61765a723b162c7067ef72df7ab9ee88a6fd0f (patch)
tree64dadd04dd9d8c26fcec7701e11122e029f6ac93
parent0865a8b81075bfe073aba56e03cc57c30bfffe00 (diff)
downloadcryptography-5f61765a723b162c7067ef72df7ab9ee88a6fd0f.tar.gz
cryptography-5f61765a723b162c7067ef72df7ab9ee88a6fd0f.tar.bz2
cryptography-5f61765a723b162c7067ef72df7ab9ee88a6fd0f.zip
remove SSL_OP_MSIE_SSLV2_RSA_PADDING
According to the header it ahs had "no effect singe 0.9.7h and 0.9.8b" but more importantly they decided to re-use the constant (wtf?) in an upcoming OpenSSL release so anybody running bleeding edge will get an undefined symbol To see the commit where they reused the define: https://github.com/openssl/openssl/commit/dece3209f299ebcd82414868ee39b2c6feb3be0a
-rw-r--r--cryptography/hazmat/backends/openssl/ssl.py1
1 files changed, 0 insertions, 1 deletions
diff --git a/cryptography/hazmat/backends/openssl/ssl.py b/cryptography/hazmat/backends/openssl/ssl.py
index 3fd0bf23..77185dfd 100644
--- a/cryptography/hazmat/backends/openssl/ssl.py
+++ b/cryptography/hazmat/backends/openssl/ssl.py
@@ -54,7 +54,6 @@ static const int SSL_OP_NETSCAPE_CHALLENGE_BUG;
static const int SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG;
static const int SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG;
static const int SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER;
-static const int SSL_OP_MSIE_SSLV2_RSA_PADDING;
static const int SSL_OP_SSLEAY_080_CLIENT_DH_BUG;
static const int SSL_OP_TLS_D5_BUG;
static const int SSL_OP_TLS_BLOCK_PADDING_BUG;