Skip to content
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

Validate that AesGcmSpi#engineInit gets non-null key #146

Merged
merged 6 commits into from
Mar 13, 2021

Conversation

alex-chew
Copy link
Contributor

Issue #, if available: #144

Description of changes: Ensure that all initialization paths in AesGcmSpi validate that the passed Key is non-null, like RsaCipher does.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

alex-chew and others added 3 commits March 12, 2021 09:35
Co-authored-by: SalusaSecondus <SalusaSecondus@users.noreply.github.com>
@alex-chew
Copy link
Contributor Author

A test failed in the accp_github_pr build, but it was unrelated to these changes and I couldn't reproduce the failure on my machine. Re-running the build.

Copy link
Contributor

@SalusaSecondus SalusaSecondus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alex-chew alex-chew merged commit 6bead18 into corretto:develop Mar 13, 2021
@alex-chew alex-chew deleted the aes-gcm-spi-no-null-key branch March 13, 2021 00:56
SalusaSecondus added a commit to SalusaSecondus/amazon-corretto-crypto-provider that referenced this pull request Apr 15, 2021
* develop:
  Remove dead code and bump patch version
  Add logic to generate a classpath file
  Clarify best practices are local to ACCP
  Improve documentation (corretto#151)
  Update CHANGELOG for 1.6.0 (corretto#148)
  Handle RsaCipher#engineDoFinal with no input bytes (corretto#147)
  Validate that AesGcmSpi#engineInit gets non-null key (corretto#146)
  Move to OpenSSL 1.1.1j (corretto#145)
  Add list of known differences (corretto#137)
  Better output size estimates. Fixes corretto#135
  Move to openssl 1.1.1i (corretto#136)
  Initial commit of the development guide (corretto#134)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants