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

Linter: gosec, Rule: G505 - Import blocklist: crypto/sha1. Should we enable it? #12954

Closed
zak-pawel opened this issue Mar 26, 2023 · 2 comments · Fixed by #13021
Closed

Linter: gosec, Rule: G505 - Import blocklist: crypto/sha1. Should we enable it? #12954

zak-pawel opened this issue Mar 26, 2023 · 2 comments · Fixed by #13021
Labels

Comments

@zak-pawel
Copy link
Collaborator

Use Case

This issue starts discussion about enabling:

Rule is mapped to CWE-327: Use of a Broken or Risky Cryptographic Algorithm.

Expected behavior

Decision if rule should be enabled or not.

Actual behavior

For this rule following findings were found in current code:

plugins/inputs/webhooks/artifactory/artifactory_webhook.go:5:2  gosec  G505: Blocklisted import crypto/sha1: weak cryptographic primitive
plugins/inputs/webhooks/github/github_webhooks.go:5:2           gosec  G505: Blocklisted import crypto/sha1: weak cryptographic primitive

Additional info

For this rule no additional configuration can be provided.

@powersj
Copy link
Contributor

powersj commented Mar 27, 2023

+1

@srebhan
Copy link
Member

srebhan commented Apr 3, 2023

So what do we do with the locations requiring SHA1 due to the queried endpoint? +1 if the idea is to consciously silence those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants