diff options
| author | David Benjamin <davidben@davidben.net> | 2018-06-29 19:28:33 -0400 |
|---|---|---|
| committer | Paul Kehrer <paul.l.kehrer@gmail.com> | 2018-06-29 16:28:33 -0700 |
| commit | 8bf42606a35611c804c2204106cd84f436550ccb (patch) | |
| tree | 3cbe0b6be0bee5683a6b7c696bc1acfd9ad9982f /src/_cffi_src/openssl/ecdsa.py | |
| parent | 3367806cd464fac96abd1b8416700ad174e8b64d (diff) | |
| download | cryptography-8bf42606a35611c804c2204106cd84f436550ccb.tar.gz cryptography-8bf42606a35611c804c2204106cd84f436550ccb.tar.bz2 cryptography-8bf42606a35611c804c2204106cd84f436550ccb.zip | |
Revert the const bits of #4220. (#4276)
In #4220, I switched BIO_new to take a const pointer (true in 1.1.0, but
not 1.0.2) on grounds that:
This also folds in the const bits from 1.1.0, on the assumption that,
now that the function pointer check is gone, it will just cause cffi to
generate more conservative pointer types that work for 1.0.2 as well.
But I got this backwards. If the bindings say BIO_METHOD*, cffi will
pass a BIO_METHOD* to BIO_new, which works in both OpenSSL versions. If
it says const BIO_METHOD*, cffi will pass const BIO_METHD* to BIO_new,
which does not work in 1.0.2.
(Although cryptography.io's build ignores all these warnings anyway, so
it's kind of moot.)
Diffstat (limited to 'src/_cffi_src/openssl/ecdsa.py')
0 files changed, 0 insertions, 0 deletions