Fixup the KmsKeyring spec to prefer GDK
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the KmsKeyring spec and compare its expectations with the exceptions added in pull request 143. Update the spec so GDK is preferred, using Encrypt only when the Materials already contain an existing data key, and confirm the expected behavior through the relevant spec tests.
Written by the indexing model from the issue text.
Description
See https://github.com/aws/amazon-s3-encryption-client-python/pull/143 and the exceptions added there.
The spec was written to imply Encrypt is the preferred KMS API, but it should be GDK first,
and only (maybe/should) use Encrypt when the Materials already have an existing data key.
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 2
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.
More from aws/amazon-s3-encryption-client-python
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in aws/amazon-s3-encryption-client-python
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·