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

SHA512/256 #53

Merged
merged 12 commits into from
Oct 25, 2024
Merged

SHA512/256 #53

merged 12 commits into from
Oct 25, 2024

Conversation

mborland
Copy link
Member

Implements SHA512/256 and makes a simplification to all of the classes. Rather than inheriting into an empty class the hashers are now a simple Alisas from a using = statement. This avoids a hasher being 3 levels of classes.

Closes: #52
Closes: #25

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://53.crypt.prtest2.cppalliance.org/libs/crypt/doc/html/index.html

Copy link

codecov bot commented Oct 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (0296d5a) to head (cf78ef4).
Report is 13 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff             @@
##           develop       #53    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           36        40     +4     
  Lines         1890      2083   +193     
  Branches       220       241    +21     
==========================================
+ Hits          1890      2083   +193     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mborland mborland merged commit 06eff7d into develop Oct 25, 2024
71 checks passed
@mborland mborland deleted the sha512-256 branch October 25, 2024 18:24
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.

SHA-512/256 Level 2: SHA-2 (256-bit)
2 participants