-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
WASM: Add SHA* hash functions #40486
Conversation
src/libraries/System.Security.Cryptography.Algorithms/tests/IncrementalHashTests.cs
Outdated
Show resolved
Hide resolved
src/libraries/System.Security.Cryptography.Algorithms/tests/IncrementalHashTests.cs
Outdated
Show resolved
Hide resolved
Seeing as you added me I question the need for any of this. Is there a driving customer requirement for parity in WASM? |
Marking this no merge for now while we work through compliance-related details. |
Yes, this is needed |
Unmarking no merge per email thread from this morning. But please make the requested changes at your convenience. :) |
This ports the managed SHA* hash functions from https://github.com/microsoft/referencesource so we can use them on Browser/WASM where we don't have OpenSSL. Enables the System.Security.Cryptography.Algorithms tests for these classes: `Tests run: 271, Errors: 0, Failures: 0, Skipped: 1. Time: 11.028473s` Resolves dotnet#40076
3f0d0ca
to
c28de45
Compare
Updated the PR:
|
/backport to release/5.0-rc2 |
Started backporting to release/5.0-rc2: https://github.com/dotnet/runtime/actions/runs/236751870 |
This ports the managed SHA* hash functions from https://github.com/microsoft/referencesource so we can use them on Browser/WASM where we don't have OpenSSL.
Enables the System.Security.Cryptography.Algorithms tests for these classes:
Tests run: 271, Errors: 0, Failures: 0, Skipped: 1. Time: 11.857137s
Resolves #40076
(related: implement this using the web crypto APIs in .NET6: #40074)