-
Notifications
You must be signed in to change notification settings - Fork 158
style: enable gosec linter #1202
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think high level feedback: the linter isn't always right - it is a guideline, not a hard rule
Co-authored-by: Stephen Buttolph <[email protected]> Signed-off-by: Jonathan Oppenheimer <[email protected]>
99dafde
to
d960769
Compare
Signed-off-by: Jonathan Oppenheimer <[email protected]>
utils/rand/rand.go
Outdated
"math" | ||
) | ||
|
||
func SecureFloat64() float64 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is somewhat terrifying. I don't know how this works. Not sure I can really review this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated the implementation to this: https://brandur.org/fragments/crypto-rand-float64.
Only issue is now copyright. Is this acceptable? I added attribution.
Why this should be merged
This PR works towards completing #1144.