-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
gh-141801: Use accessors for ASN1_STRING fields #141802
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
Conversation
While ASN1_STRING is currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL's X509 objects could be much more memory-efficient.
|
Don't think this needs a NEWS entry, but happy to add one if you all prefer:
|
picnixz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When were those macros added? and are they available on alternative implementations of libssl?
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
1.1.0 I believe. And yes, they're in BoringSSL and LibreSSL. |
|
Considering AWS-LC tests are fine, I think we can make that change. |
…onGH-141802) * pythongh-141801: Use accessors for ASN1_STRING fields While ASN1_STRING is currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL's X509 objects could be much more memory-efficient. * Update Modules/_ssl.c Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> * Update Modules/_ssl.c Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> --------- (cherry picked from commit c41fce0) Co-authored-by: David Benjamin <davidben@davidben.net> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
GH-141847 is a backport of this pull request to the 3.14 branch. |
…onGH-141802) * pythongh-141801: Use accessors for ASN1_STRING fields While ASN1_STRING is currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL's X509 objects could be much more memory-efficient. * Update Modules/_ssl.c Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> * Update Modules/_ssl.c Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> --------- (cherry picked from commit c41fce0) Co-authored-by: David Benjamin <davidben@davidben.net> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
GH-141848 is a backport of this pull request to the 3.13 branch. |
…141802) (#141847) gh-141801: Use accessors for ASN1_STRING fields in libssl (GH-141802) * gh-141801: Use accessors for ASN1_STRING fields While ASN1_STRING is currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL's X509 objects could be much more memory-efficient. * Update Modules/_ssl.c * Update Modules/_ssl.c --------- (cherry picked from commit c41fce0) Co-authored-by: David Benjamin <davidben@davidben.net> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…141802) (#141848) gh-141801: Use accessors for ASN1_STRING fields in libssl (GH-141802) * gh-141801: Use accessors for ASN1_STRING fields While ASN1_STRING is currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL's X509 objects could be much more memory-efficient. * Update Modules/_ssl.c * Update Modules/_ssl.c --------- (cherry picked from commit c41fce0) Co-authored-by: David Benjamin <davidben@davidben.net> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
While
ASN1_STRINGis currently exposed, it is better to use the accessors. See openssl/openssl#29117 where, if the type were opaque, OpenSSL'sX509objects could be much more memory-efficient.