-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add API for getting the method of a Context object #61
Comments
Yes. This would be nice. |
Perhaps the reason there is not yet any binding, though, is that there is no obvious OpenSSL API for accessing this information. |
I suppose it's possible to just reach in and inspect the First cryptography will need to be updated to expose some SSL_CTX guts, though. |
Cool! I'll file a bug and link to this one. |
Partially deopaque SSL_CTX to support a pyopenssl use case This allows PyOpenSSL to access the "method" field of the SSL_CTX struct, which allows you to see the method of an already existing context. This is useful, for example, for debugging and testing. The relevant PyOpenSSL ticket is pyca/pyopenssl#61. Fixes #783.
Cryptography has now grown support for this, so we can use it as soon as we require the next version of it. However, the cryptography project does not have unit tests for this feature since they themselves do not consume that API; so we will want them in PyOpenSSL. (We'd want them anyway, of course.) |
Partially deopaque SSL_CTX to support a pyopenssl use case This allows PyOpenSSL to access the "method" field of the SSL_CTX struct, which allows you to see the method of an already existing context. This is useful, for example, for debugging and testing. The relevant PyOpenSSL ticket is pyca/pyopenssl#61. Fixes #783.
See also pyca/cryptography#841 ; we will need to use a |
Could be that I've missed this in the documentation, but there does not appear to be a way to access the method (as in
SSLv23_METHOD
) of an already existing context.I want this for writing tests.
The text was updated successfully, but these errors were encountered: