-
Notifications
You must be signed in to change notification settings - Fork 1
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
Recursive hashing #29
Comments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CHVote Algorithm 4.14 hashes each component of an array or matrix separately, and then hashes those together.
"it is important to ensure that collisions can not occur in a trivial manner.
This happens for example when applying the hash algorithm directly to the concatenated
byte arrays. A general approach to circumvent this type of problem is to first apply the hash
algorithm individually to each Bi and then to the concatenation of the obtained hashes"
Currently this is only used in computing the challenge.
ElectionGuard does not use recursive hashing, but it does use Hmac based on SHA-256 instead of plain SHA-256:
instead of
Is that why they dont need recursive hashing?
The text was updated successfully, but these errors were encountered: