[fix](be) Mask sensitive fields in encryption keys schema table - #66834
Open
dzr171712 wants to merge 1 commit into
Open
[fix](be) Mask sensitive fields in encryption keys schema table#66834dzr171712 wants to merge 1 commit into
dzr171712 wants to merge 1 commit into
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Author
|
run buildall |
1 similar comment
Contributor
|
run buildall |
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
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.
What problem does this PR solve?
Issue Number: close #CIR-27838
Related PR: #xxx
Problem Summary:
Querying
information_schema.encryption_keysexposes the original Base64-encoded initialization vector and ciphertext through theIVandCIPHERcolumns.The schema scanner previously copied
iv_base64andciphertext_base64directly into the result block. This change masks both fields with******when their values are present, while preserving the existing empty-string behavior when the fields are absent.A BE unit test is added to verify both the masked-value and empty-value cases.
Release note
None
Check List (For Author)
Test
Behavior changed:
IVandCIPHERcolumns ininformation_schema.encryption_keysnow return******instead of exposing their original values.Does this need documentation?
Check List (For Reviewer who merge this PR)