Support content encryption within CentralDogma
Open
Nobody has claimed this yet.
new feature
priority: P0
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
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:
- Users can register a key[s] when creating a repository.
- The registered key[s] encrypt the content when stored.
- Users send over a private key when reading/modifying content. Alternatively, the encrypted content could be fetched and decrypted using a user's private key locally.
caveats:
- Each file content would be encrypted, but the directory structure will still be visible
- We should make sure that the encryption/decryption is performant since central dogma may host a large number of files with reasonable size (10MB~)
- TBU...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Begin by tracing repository creation and content read/write flows, then clarify the encryption, key registration, private-key handling, visibility, and performance requirements before defining what a complete implementation would require.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100