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 OpenSSL 3's KBKDF for SP800-108 if it is available #106779

Merged
merged 10 commits into from
Aug 23, 2024

Conversation

vcsjones
Copy link
Member

If OpenSSL 3 is not available, or KBKDF is not present, then the managed implementation will continue to be used. This does not impact The Microsoft.Bcl.Cryptography package.

If OpenSSL 3 is not available, or KBKDF is not present, then the managed implementation will continue to be used. This does not impact The Microsoft.Bcl.Cryptography package.
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

@vcsjones vcsjones changed the title Use OpenSSL 3's KBKDF for SP800-108 if it available Use OpenSSL 3's KBKDF for SP800-108 if it is available Aug 21, 2024
@vcsjones vcsjones marked this pull request as ready for review August 22, 2024 00:27
@vcsjones vcsjones merged commit 6c83f94 into dotnet:main Aug 23, 2024
96 of 98 checks passed
@vcsjones vcsjones added this to the 10.0.0 milestone Aug 23, 2024
@vcsjones vcsjones deleted the ossl3-kbkdf branch August 23, 2024 18:12
@vcsjones
Copy link
Member Author

/backport to release/9.0

Copy link
Contributor

Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/10530440871

@vcsjones vcsjones added the cryptographic-docs-impact Issues impacting cryptographic docs. Cleared and reused after documentation is updated each release. label Aug 23, 2024
Copy link
Contributor

@vcsjones backporting to release/9.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Applying: Use OpenSSL 3's KBKDF for SP800-108 if it available.
Applying: Add missing string consts to compat
Applying: Fix name of unused parameters in fallback
Applying: Code review feedback
Patch is empty.
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

Copy link
Contributor

@vcsjones an error occurred while backporting to release/9.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

akoeplinger pushed a commit to dotnet/arcade that referenced this pull request Aug 29, 2024
If the pull request being back ported contains an empty commit, the backport command will fail during `git am` since it has not been instructed what to do with an empty commit.

This changes the backport command to preserve the empty commit.

See this pull request from `dotnet/runtime` for an example of the backport command failing in the presence of an empty commit: dotnet/runtime#106779
@bartonjs bartonjs removed the cryptographic-docs-impact Issues impacting cryptographic docs. Cleared and reused after documentation is updated each release. label Sep 4, 2024
@bartonjs
Copy link
Member

bartonjs commented Sep 4, 2024

Note to future me: cryptograhic-docs-impact was removed because it's being incorporated in the 9.0 docs.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants