Skip to content
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

Use the newer names for STACK_OF(T) functions with BoringSSL #2231

Merged
merged 1 commit into from
May 2, 2024

Conversation

davidben
Copy link
Contributor

@davidben davidben commented May 1, 2024

This is yet another symptom of #1944.

Ideally rust-openssl would use the type-safe wrappers, which are the actual public APIs. Right now, rust-openssl's STACK_OF(T) handling is a safety regression from C. This PR doesn't address the safety issue, only works around the BoringSSL porting issue.

This is yet another symptom of
sfackler#1944.

Ideally rust-openssl would use the type-safe wrappers, which are the
actual public APIs. Right now, rust-openssl's STACK_OF(T) handling is a
safety regression from C. This PR doesn't address the safety issue, only
works around the BoringSSL porting issue.
@alex alex merged commit 1088c1d into sfackler:master May 2, 2024
61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants