Skip to content
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.

Sign up for GitHub

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

Suggest Log Redaction when using TDE #6147

Merged
merged 2 commits into from
Aug 12, 2021
Merged

Suggest Log Redaction when using TDE #6147

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21d8bfb
TDE-log-redaction
dveeden Aug 11, 2021
477e80c
minor fix
TomShawn Aug 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion encryption-at-rest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The current version of TiKV encryption has the following drawbacks. Be aware of
* TiFlash supports encryption at rest since v4.0.5. For details, refer to [Encryption at Rest for TiFlash](#encryption-at-rest-for-tiflash-new-in-v405). When deploying TiKV with TiFlash earlier than v4.0.5, data stored in TiFlash is not encrypted.
* TiKV currently does not exclude encryption keys and user data from core dumps. It is advised to disable core dumps for the TiKV process when using encryption at rest. This is not currently handled by TiKV itself.
* TiKV tracks encrypted data files using the absolute path of the files. As a result, once encryption is turned on for a TiKV node, the user should not change data file paths configuration such as `storage.data-dir`, `raftstore.raftdb-path`, `rocksdb.wal-dir` and `raftdb.wal-dir`.
* TiKV info log contains user data for debugging purposes. The info log and this data in it are not encrypted.
* TiKV, TiDB and PD info logs can contain user data for debugging purposes. The info log and this data in it are not encrypted. It is advised to enable [Log Redaction](/log-redaction.md).
TomShawn marked this conversation as resolved.
Show resolved Hide resolved

## TiKV encryption at rest

Expand Down