-
Notifications
You must be signed in to change notification settings - Fork 18
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
Don't use md5 for computing the lockfile filename #212
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #212 +/- ##
==========================================
- Coverage 94.93% 94.92% -0.01%
==========================================
Files 9 9
Lines 1105 1103 -2
Branches 229 229
==========================================
- Hits 1049 1047 -2
Misses 42 42
Partials 14 14 ☔ View full report in Codecov by Sentry. |
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.
for futureproofing you might want to add usedforsecurity=False on sha256 as that algorithm is on its way out also.
2423eb3
to
937d04a
Compare
md5 is forbidden in FIPS mode, rely on sha3-256 instead
For $reasons, python 3.12.4 causes issues with Sphinx no longer correctly recognizing its nitpicky allowlist when performing a `from $smth import foo`. But `import $smth` and then using `$smth.foo` directly works, so we use that ¯\_(ツ)_/¯
md5 is forbidden in FIPS mode, rely on SHA256 instead
This fixes #213