awslabs / awslabs/aws-encryption-sdk-specification
implementation: follow-up to refactoring CMC spec
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Follow-up for #166.
- C
- [ ] Accept local CMC capacity values below 2: aws/aws-encryption-sdk-c#562
- JavaScript
- [ ] Accept local CMC capacity value of 0: aws/aws-encryption-sdk-javascript#397
- Python
- [ ] Accept TTL in local CMC's put_decryption_materials: aws/aws-encryption-sdk-python#285
- [ ] Accept local CMC capacity value of 0: aws/aws-encryption-sdk-python#289
Contributor guide
Research direction
Review issue #166 first, then follow the linked C, JavaScript, and Python implementation issues to understand the remaining CMC behavior changes. Done means the listed capacity and TTL cases are implemented in the relevant SDKs and the specification follow-up is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, javascript, python
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100