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

Fixes and improvements for wolfTPM CSR wrappers #307

Merged
merged 4 commits into from
Oct 23, 2023

Conversation

dgarske
Copy link
Contributor

@dgarske dgarske commented Oct 18, 2023

  • Fix for trying to use a custom wolfTPM CSR sigType. The csr->req.sigType was being initialized to CTC_SHA256wRSA, and not allowing override.
  • Add wrapper support for setting key usage (not just extended key usage).
  • Fix support for ECC 384-bit only support. Tested with: ./configure --enable-wolftpm CFLAGS="-DECC_USER_CURVES -DNO_ECC256 -DHAVE_ECC384" --disable-examples --disable-crypttests && make
  • Add CI tests for CSharp wrappers.

…igType` was being initialized to CTC_SHA256wRSA, and not allowing override.
@dgarske
Copy link
Contributor Author

dgarske commented Oct 19, 2023

I am going to add a test case for this.

…-enable-wolftpm CFLAGS="-DECC_USER_CURVES -DNO_ECC256 -DHAVE_ECC384" --disable-examples --disable-crypttests && make`
@dgarske dgarske changed the title Fix for trying to use a custom wolfTPM CSR sigType Fixes and improvements for wolfTPM CSR wrappers Oct 20, 2023
@dgarske dgarske force-pushed the csr_sigtype branch 2 times, most recently from acbbf06 to de35c64 Compare October 23, 2023 16:08
Copy link
Contributor

@jpbland1 jpbland1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@jpbland1 jpbland1 merged commit 45847e3 into wolfSSL:master Oct 23, 2023
1 check passed
@dgarske dgarske deleted the csr_sigtype branch December 29, 2023 17:42
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.

4 participants