Added support for AES-CTR in PKCS11 driver #9277
Merged
Conversation
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
Contributor
|
🛟 Devin Lifeguard found 1 likely issues in this PR
@danielinux |
Contributor
|
Jenkins retest this please. Generic DTLS config "FAIL scripts/openssl.test (exit status: 1)" |
danielinux
requested review from
wolfSSL-Bot
and removed request for
LinuxJedi
Contributor
|
Jenkins retest this please: "FIPSv2-regression" |
dgarske
approved these changes
Oct 7, 2025
dgarske
approved these changes
Oct 7, 2025
Contributor
dgarske
left a comment
dgarske
left a comment
There was a problem hiding this comment.
Over to @SparkiDev to finalize.
Member
Author
|
tested via wolfSSL/wolfPKCS11#148 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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
Add support for AES_CTR via wc_pkcs11.c
Proposed fix for zd#20548
Testing
interop test suite within wolfPKCS11