-
Notifications
You must be signed in to change notification settings - Fork 114
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
Support content encryption within CentralDogma #755
Labels
Comments
Instead, we could consider encrypting the entire repository? https://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/ |
minwoox
added a commit
to minwoox/centraldogma
that referenced
this issue
Nov 15, 2023
Motivation: Before we support content encryption within CentralDogma, we need a way to secure the sensitive information in mirroring configuration. We can do this using `ConfigValueConverter` that is introduced via line#890 as a temporarily workaround. Modifications: - Apply `ConfigValueConverter` to mirroring configuration. Result: - You can temporarily hide sensitive information in mirroring configuration using `ConfigValueConverter`. Please note that this feature will be deprecated after we implement line#755.
minwoox
added a commit
that referenced
this issue
Nov 23, 2023
Motivation: Before we support content encryption within CentralDogma, we need a way to secure sensitive information in mirroring configuration. We can do this using `ConfigValueConverter` that is introduced via #890 as a temporary workaround. Modifications: - Apply `ConfigValueConverter` to mirroring configuration. Result: - You can temporarily hide sensitive information in mirroring configuration using `ConfigValueConverter`. Please note that this feature will be deprecated after we implement #755.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just wanted to float this idea with other maintainers.
We may want to support data encryption within central dogma so users can save sensitive data. (and centraldogma can possibly also act as a backend for a KMS)
One idea I had was:
caveats:
The text was updated successfully, but these errors were encountered: