Skip to content

Comments

lib/crypt-sha*, lib/crypt-sm3: fix misleading comment#222

Open
RavuAlHemio wants to merge 1 commit intobesser82:developfrom
RavuAlHemio:shacrypt-comment
Open

lib/crypt-sha*, lib/crypt-sm3: fix misleading comment#222
RavuAlHemio wants to merge 1 commit intobesser82:developfrom
RavuAlHemio:shacrypt-comment

Conversation

@RavuAlHemio
Copy link

A copied comment misrepresents the calculation step of the S byte sequence in the crypt algorithms based on SHA2 and sm3. Replace it with an actual description of what is happening.

A copied comment misrepresents the calculation step of the S byte
sequence in the crypt algorithms based on SHA2 and sm3. Replace it with
an actual description of what is happening.
@solardiz
Copy link
Collaborator

Thanks. FWIW, this is one of the most ridiculous aspects of SHA-crypt - a timing leak that exists for no good reason at all (not a tradeoff, just a ridiculous extra). I previously mentioned this in: #35 (comment)

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.

2 participants