remove OpenSSL backend#2458
Merged
Merged
Conversation
LPardue
approved these changes
May 5, 2026
jannes
approved these changes
May 5, 2026
The OpenSSL backend (the `openssl` feature, backed by quictls/openssl) was incomplete: 0-RTT and custom private key signing were unsupported, several tests were disabled under it, and the underlying quictls fork is unmaintained. The BoringSSL backend code is left as-is. Comments, FFI declarations and the `tls/`, `crypto/` module layout still reflect a multi-backend setup. That can be cleaned up later without touching protocol code.
auto-merge was automatically disabled
May 5, 2026 13:10
Branch protection rule check failed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The OpenSSL backend (the
opensslfeature, backed by quictls/openssl) was incomplete: 0-RTT and custom private key signing were unsupported, several tests were disabled under it, and the underlying quictls fork is unmaintained.The BoringSSL backend code is left as-is. Comments, FFI declarations and the
tls/,crypto/module layout still reflect a multi-backend setup. That can be cleaned up later without touching protocol code.