Uh oh!
There was an error while loading. Please reload this page.
branch-4.1: [fix](security) Mask private key password in backend configuration #66836 - #66933
Merged
Merged
Conversation
…66836) Problem Summary: The `tls_private_key_password` configuration value is exposed in plaintext through `information_schema.backend_configuration`. The value is collected by `config::get_config_info()` from the BE configuration map and returned without masking. Since the default role has read access to `information_schema.*`, an authenticated user can query the table and obtain the TLS private key password. This change masks `tls_private_key_password` as `******` at the shared configuration export layer. The masking applies to `information_schema.backend_configuration` and other output paths that reuse `get_config_info()`, while preserving the configuration name, type, and mutability fields. ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [x] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [x] Other reason: The change is limited to replacing one sensitive configuration value at the shared output point. `clang-format`, `git diff --check`, and `config.cpp` compilation passed. - Behavior changed: - [ ] No. - [x] Yes. `tls_private_key_password` is now returned as `******` instead of its plaintext value.
hello-stephen
commented
Aug 19, 2026
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hello-stephen
commented
Aug 19, 2026
Contributor
run buildall |
yiguolei
approved these changes
Aug 20, 2026
ContributorAuthor
PR approved by at least one committer and no changes requested. |
ContributorAuthor
PR approved by anyone and no changes requested. |
yiguolei
commented
Aug 20, 2026
Contributor
skip buildall |
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-picked from #66836