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
@networkimprov requested issue #37118 to be considered for backport to the next 1.13 minor release.
@gopherbot please open backport, at suggestion of @FiloSottile.
The text was updated successfully, but these errors were encountered:
Approving this backport. It's a small security hardening fix.
Sorry, something went wrong.
Change https://golang.org/cl/220653 mentions this issue: [release-branch.go1.13] crypto/cipher: require non-zero nonce size for AES-GCM
[release-branch.go1.13] crypto/cipher: require non-zero nonce size for AES-GCM
Closed by merging 6f57b10 to release-branch.go1.13.
[release-branch.go1.13] crypto/cipher: require non-zero nonce size fo…
6f57b10
…r AES-GCM Also fix typo in crypto/cipher/gcm_test.go. Updates #37118 Fixes #37417 Change-Id: I8544d1eeeb1f0336cebb977b8c5bfa5e4c5ad8c7 Reviewed-on: https://go-review.googlesource.com/c/go/+/218500 Run-TryBot: Katie Hockman <katie@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org> (cherry picked from commit 4e8badb) Reviewed-on: https://go-review.googlesource.com/c/go/+/220653 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
No branches or pull requests
@networkimprov requested issue #37118 to be considered for backport to the next 1.13 minor release.
The text was updated successfully, but these errors were encountered: