-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Linter: gosec, Rule: G506 - Import blocklist: golang.org/x/crypto/md4. Should we enable it? #15801
Comments
I would enable it. |
What's the difference to rule 406 (#15800)? |
406 detects usages, 506 detects imports. I don't know why they are separated... |
I think we cannot use it if we don't import it and vice versa without triggering compiler errors or other linters. So I would say we do the one or the other not both. What do you think? |
It seems then that banning the import makes more sense. Although I don't see any objections to enabling both. :) |
See my comment in the other issue... |
Use Case
This issue starts discussion about enabling:
Rule is mapped to CWE-327: Use of Weak Hash.
Expected behavior
Decision if rule should be enabled or not.
Actual behavior
For this rule no findings were found in current code.
Additional info
For this rule no additional configuration can be provided.
The text was updated successfully, but these errors were encountered: