E2EE between Decaton client <-> processor
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 373
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
- Some applications have a requirement to encrypt message payload end-to-end for security reason
- Decaton can provide a feature for that
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
The issue names no files, tests, or entry points. Start by tracing how messages move between the Decaton client and processor, then define the encryption design and its key-handling requirements; done should mean that message payloads are encrypted end-to-end between those components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100