We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version 2.0 of the various ESDK implementations have added key commitment as another dimension of variability for algorithms suites: https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/
At a minimum we need to update the information on the available algorithm suites and especially the fact that the default algorithm suite now depends on your commitment policy: https://github.com/awslabs/aws-encryption-sdk-specification/blob/4b1c0e06435d385fc0593a5619ce686cf2cb79e8/framework/algorithm-suites.md#supported-algorithm-suites
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Version 2.0 of the various ESDK implementations have added key commitment as another dimension of variability for algorithms suites: https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/
At a minimum we need to update the information on the available algorithm suites and especially the fact that the default algorithm suite now depends on your commitment policy: https://github.com/awslabs/aws-encryption-sdk-specification/blob/4b1c0e06435d385fc0593a5619ce686cf2cb79e8/framework/algorithm-suites.md#supported-algorithm-suites
The text was updated successfully, but these errors were encountered: