chore: Switch to sha256 from md5 to remedy CodeQL Warning #3356
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
This use of md5 doesn't appear to be a cryptographically sensitive
context, but the easiest remediation for the CodeQL flags is to
switch to an approved hash function.
diondrapeck
approved these changes
Aug 20, 2024
luigiw
approved these changes
Aug 20, 2024
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 pull request migrates from md5 to sha256
azureml-examples/sdk/python/jobs/single-step/pytorch/distributed-training-yolov5/yolov5/utils/dataloaders.py
Line 106 in 6a36786
CodeQL warns against weak cryptography. This use of md5 doesn't seem to appear in a cryptographically sensitive context, but the easiest remediation for the CodeQL warnings is to switch to an approved hash function.
Checklist