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

SHA2: Use new version where possible #224

Merged
merged 8 commits into from
Feb 3, 2025
Merged

SHA2: Use new version where possible #224

merged 8 commits into from
Feb 3, 2025

Conversation

marsella
Copy link
Contributor

@marsella marsella commented Jan 23, 2025

Closes #122.

I looked through all the uses of the alternative SHA2 implementation and replaced most of them with the spec-adherent version. The remaining applications use some internal functions that aren't public in the spec-adherent version and which I'm not particularly inclined to make public without looking through the specs for the other applications.

I chose to keep the alternative SHA2 version and rename it SHA2Internal. I documented the uses in the hash readme. I'm also open to deleting it and all its dependencies -- an implementation of SHACAL and one of HMAC. (There are two versions of HMAC in the repo, one of which I was able to switch to use the spec-adherent SHA2 -- see also #157)

@marsella marsella mentioned this pull request Jan 27, 2025
@marsella marsella merged commit 3ec8dc2 into master Feb 3, 2025
2 checks passed
@marsella marsella deleted the 122-replace-sha2 branch February 3, 2025 18:40
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.

Replace uses of imperative SHA2 with spec-adherent SHA2
2 participants