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

Remove duplicates and tidy tags to resolve #2523 #2536

Merged

Conversation

tghosth
Copy link
Collaborator

@tghosth tghosth commented Jan 19, 2025

This Pull Request relates to issue #2523

@elarlang
Copy link
Collaborator

elarlang commented Jan 19, 2025

Missing . before new sentence.

"should" vs "must"?

Level 1 really depends on context.

@tghosth
Copy link
Collaborator Author

tghosth commented Jan 20, 2025

Fixed those 3 issues @elarlang

@tghosth tghosth marked this pull request as ready for review January 20, 2025 18:32
@tghosth tghosth enabled auto-merge (squash) January 20, 2025 18:32
@tghosth tghosth merged commit 2111ba5 into master Jan 20, 2025
6 checks passed
@tghosth tghosth deleted the 2523-redundant-requirement-about-secure-hash-functions branch January 20, 2025 18:37
@@ -96,10 +96,9 @@ Cryptographic hashes are used in a wide variety of cryptographic protocols, such

| # | Description | L1 | L2 | L3 | CWE |
| :---: | :--- | :---: | :---: | :---: | :---: |
| **6.6.1** | [ADDED] Verify that only approved hash functions are used for general cryptographic use cases, including digital signatures, HMAC, KDF, and random bit generation. | | ✓ | ✓ | |
| **6.6.1** | [ADDED, SPLIT FROM 6.2.5, COVERS 6.2.3] Verify that only approved hash functions are used for general cryptographic use cases, including digital signatures, HMAC, KDF, and random bit generation. Disallowed hash functions, such as MD5, SHA-1, must not be used for any cryptographic purpose. | | ✓ | ✓ | |
Copy link
Contributor

@randomstuff randomstuff Jan 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disallowed hash functions, such as MD5, SHA-1, must not be used for any cryptographic purpose.

There is some inconsitency here as HMAC-SHA-1 is currently allowed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per #2399

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Therefore I would suggest using:

[ADDED, SPLIT FROM 6.2.5, COVERS 6.2.3] Verify that only approved hash functions are used for general cryptographic use cases, including digital signatures, HMAC, KDF, and random bit generation. Disallowed hash functions, such as MD5, must not be used for any cryptographic purpose.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any situation where MD5 would be allowed? Can you open a PR @randomstuff ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tghosth, this is #2546

@jmanico
Copy link
Member

jmanico commented Jan 21, 2025 via email

@randomstuff
Copy link
Contributor

randomstuff commented Jan 21, 2025

@jmanico, Yes my point was that we are saying in one place that “SHA-1 must not be used for any cryptographic purpose” but in some other place that using SHA-1 as part of the HMAC construct is allowed.

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.

Redundant requirement about secure hash functions
4 participants