go: weak bcrypt cost #128
Open
go: weak bcrypt cost #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
burntcarrot
force-pushed
the
rule-go-bcrypt-cost
branch
from
626c1f5 to
c7dfef4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This checker detects the usage of bcrypt.GenerateFromPassword with a cost factor less than 10. The bcrypt algorithm is designed to be computationally expensive to protect passwords against brute-force attacks. A low cost factor reduces the computational effort, making it easier for attackers to crack passwords. This checker is flagged as a security warning to ensure bcrypt is configured with a sufficiently high cost factor.
Recommendations
Use a cost factor of 10 or higher when calling bcrypt.GenerateFromPassword. OWASP recommends a cost factor of at least 10, and it should be increased as computing power grows. Adjust the cost factor based on performance testing to ensure it provides adequate security without causing unacceptable delays.
References