Wishlist / reminders for a new protocol format
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
This issue is to keep track of things that should be changed / improved when we want to update SOPS's encrypted file format.
-
MAC:
- Do not ignore
nullvalues: https://github.com/getsops/sops/issues/828 - Include keys in MAC computation to avoid problem described in https://github.com/getsops/sops/issues/52#issuecomment-2566569931
- Do not ignore
-
Encrypted data:
- Add padding to not fully reveal the length of the clear text data (https://github.com/getsops/sops/issues/815)
- Eventually even encrypt
null: https://github.com/getsops/sops/issues/828#issuecomment-796132557 - Use protobuf instead of own format: https://github.com/getsops/sops/issues/815#issuecomment-785158790
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
Start by reading the linked issues 828, 52, and 815 to understand the protocol concerns and prior discussion. Done would require a settled scope and design covering MAC handling, encrypted-data padding and nulls, and whether to use protobuf for the new format.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100