#106307Use HMAC-SHA256 where applicable
Description
- Replace current HMAC-SHA1 by stronger hashing algorithm.
- Consider updating
cHashto use (stronger) HMAC as well
Quote on HMAC-SHA1 (document viewed March 5th, 2025)
> HMAC-SHA1 SHA1 is not a collision-resistant hash function. The generation of SHA1 collisions, while requiring moderate effort, is practically possible [75, 74, 107], even though, according to current knowledge, there are no known weaknesses when using SHA1 in constructions that do not require collision resistance (for example, as the basis for an HMAC, as part of the mask generation function in RSA-OAEP, or as a component of a pseudorandom number generator). However, as a basic security measure, it is recommended to use a hash function of the SHA2 or SHA3 family in these applications as well.
Reviews 5
- main 95213[BUGFIX] Create file dump tokens with SHA3-256 everywhere
- 14.3 95219[BUGFIX] Create file dump tokens with SHA3-256 everywhere
- main 94259[!!!][TASK] Remove legacy cHash fallback (fallbackToLegacyHash)
- main 91815[!!!][TASK] Use stronger cryptographic algorithm for HMAC
- main 91829[DOCS] Correct admonition syntax in changelog file