-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: Support AWS Cryptographic Material Providers Library (MPL) #685
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very large PR.
Giving it a once-over it looks good.
You should get a few more eyes on it than me, but from what I see it looks good.
I would like to see a more clear link to the test vectors so I can wrap my mind around the... scope of testing :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we checking in bin files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this is just how Ritvik wrote the performance tests -- the tests take in a file and decrypt/encrypt it many times. We should probably rewrite this to generate files on the fly for our own testing at some point
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small nit in the error message
Co-authored-by: José Corella <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the extra tests!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Following this PR, we (pyca/cryptography) are seeing that our CI where we run aws-encryption-sdk-python's tests is failing: https://github.com/pyca/cryptography/actions/runs/11807967227/job/32895677501?pr=11941 Is this expected? Do we need to be doing something more, or is this an issue to be resolved on teh aws-encryption-sdk-python side? |
Hi @alex, This is expected. I opened a PR to cryptography to update the invocation: https://github.com/pyca/cryptography/pull/11942/files |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: