feat: sanitize auxiliary potentially sensitive fields. #12
Conversation
This file contains hidden or 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
Signed-off-by: i4k <[email protected]>
Signed-off-by: i4k <[email protected]>
i4ki
force-pushed
the
i4k-sanitive-file-hashes
branch
from
b6ed8f7 to
46838a6
Compare
snakster
approved these changes
Jul 19, 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.
For each sensitive
<field>, this also sanitize<field>_<auxiliary>if it exists and is notnull, whereauxiliaryare: "base64", "base64sha1", "base64sha256", "base64sha512", "md5", "sha1", "sha256", "sha512".