-
Notifications
You must be signed in to change notification settings - Fork 742
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
Add configuration hide-user-data-from-log to hide user data from server logs #877
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #877 +/- ##
============================================
- Coverage 70.43% 70.42% -0.02%
============================================
Files 113 114 +1
Lines 61728 61647 -81
============================================
- Hits 43479 43413 -66
+ Misses 18249 18234 -15
|
In the client info we have two extra pieces of information, the |
@valkey-io/core-team Overall would like a vote for this. In addition, some specific questions for this feature:
If we don't believe users should be logged, we should also hide them from the client list output that is also in the log. |
If Redis has already picked this name and the behavior is similar, I think this name is good (so users don't have to learn a new concept). Though from a quick look at the PR, we also use this config to decide whether to log the stack trace, which makes "user-data" a bit far fetched IMO - just a nit. |
|
I'm aligned with this. Let's remove the name and username from the client output as well. |
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.
When it comes to masking the client's name and username from the client output, should we apply it to all instances where client information is printed, or only to the cases where the server voluntarily reveals such details?
i.e. should client list
and client info
work normaly when feature is enabeld?
@hwware @madolson
@naglera I think a bunch of tests are failing because we changed the default value, which is breaking a bunch of log scans for tests. I think for testing we can default to having it on. |
Signed-off-by: naglera <[email protected]>
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.
The new code LGTM.
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.
LGTM
Signed-off-by: Madelyn Olson <[email protected]>
Minor changes to wording Signed-off-by: Madelyn Olson <[email protected]>
…er logs (#877) Implement data masking for user data in server logs and diagnostic output. This change prevents potential exposure of confidential information, such as PII, and enhances privacy protection. It masks all command arguments, client names, and client usernames. Added a new hide-user-data-from-log configuration item, default yes. --------- Signed-off-by: Amit Nagler <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]>
Minor cleanup, introduced in #877. Signed-off-by: Binbin <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
…er logs (valkey-io#877) Implement data masking for user data in server logs and diagnostic output. This change prevents potential exposure of confidential information, such as PII, and enhances privacy protection. It masks all command arguments, client names, and client usernames. Added a new hide-user-data-from-log configuration item, default yes. --------- Signed-off-by: Amit Nagler <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
…er logs (valkey-io#877) Implement data masking for user data in server logs and diagnostic output. This change prevents potential exposure of confidential information, such as PII, and enhances privacy protection. It masks all command arguments, client names, and client usernames. Added a new hide-user-data-from-log configuration item, default yes. --------- Signed-off-by: Amit Nagler <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
…er logs (valkey-io#877) Implement data masking for user data in server logs and diagnostic output. This change prevents potential exposure of confidential information, such as PII, and enhances privacy protection. It masks all command arguments, client names, and client usernames. Added a new hide-user-data-from-log configuration item, default yes. --------- Signed-off-by: Amit Nagler <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in valkey-io#877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Minor cleanup, introduced in #877. Signed-off-by: Binbin <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Implement data masking for user data in server logs and diagnostic output. This change prevents potential exposure of confidential information, such as PII, and enhances privacy protection. It masks all command arguments, client names, and client usernames.
Added a new hide-user-data-from-log configuration item, default yes.