Document the AWS-LC provider - #3434
Open
geedo0 wants to merge 2 commits into
Open
Conversation
This was referenced Aug 20, 2026
Contributor
|
🔒 Security Review — View Report Please review before merging. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## provider-sha256 #3434 +/- ##
===================================================
+ Coverage 78.27% 78.51% +0.24%
===================================================
Files 698 699 +1
Lines 124590 124622 +32
Branches 17288 17291 +3
===================================================
+ Hits 97519 97850 +331
+ Misses 26147 25846 -301
- Partials 924 926 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
geedo0
force-pushed
the
provider-readme
branch
from
August 20, 2026 15:07
896d62b to
73cf88a
Compare
geedo0
force-pushed
the
provider-readme
branch
from
August 20, 2026 15:45
73cf88a to
8b1bbf1
Compare
geedo0
force-pushed
the
provider-readme
branch
from
August 20, 2026 16:24
5ac2ebc to
5276086
Compare
geedo0
marked this pull request as ready for review
August 20, 2026 16:31
justsmth
reviewed
Aug 21, 2026
| @@ -0,0 +1,160 @@ | |||
| # aws-lc-provider | |||
|
|
|||
| An OpenSSL 3.x [provider](https://docs.openssl.org/3.0/man7/provider/) that implements no | |||
Contributor
There was a problem hiding this comment.
- We say "3.x" and link to "3.0" documentation, but we only support versions >= 3.5+?
- Will the provided be compatible with OpenSSL 4.x?
Contributor
Author
There was a problem hiding this comment.
Good catch, let me rework this section by hand. The significance of 3.x is the introduction of the provider interface and new APIs. 3.5 is the minimum required version for aws-lc-provider due to its introduction of the KEM operation. We will be compatible with 4.x and beyond for as long as OpenSSL maintains forward compatibility.
justsmth
previously approved these changes
Aug 31, 2026
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.
Description of changes:
This change documents how to build, test, install, activate, and verify the
AWS-LC provider. It includes configuration-file and programmatic activation
examples, explains the optional
?provider=awslcpreference and default-providerfallback, and describes the frontend/backend source layout.
It also adds
ALGORITHM_SUPPORT.md, organized by OpenSSL operation class, withSHA2-256 recorded as the provider's initial supported algorithm.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.