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
@rsc requested issue #41147 to be considered for backport to the next 1.19 minor release.
@gopherbot please backport
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/449016 mentions this issue: [release-branch.go1.19] crypto/x509: allow BoringCrypto to use 4096-bit keys
[release-branch.go1.19] crypto/x509: allow BoringCrypto to use 4096-bit keys
Sorry, something went wrong.
Closed by merging 861ba02 to release-branch.go1.19.
[release-branch.go1.19] crypto/x509: allow BoringCrypto to use 4096-b…
861ba02
…it keys FIPS-140 has been updated to allow 4096-bit RSA keys. Allow them in certificate processing. For #41147. Fixes #56672. Change-Id: I4c6bcb1b137a200dfe70cebc605ae57f49871184 Reviewed-on: https://go-review.googlesource.com/c/go/+/447655 Run-TryBot: Russ Cox <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Auto-Submit: Russ Cox <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/go/+/449016
a8ce6fd
…it keys FIPS-140 has been updated to allow 4096-bit RSA keys. Allow them in certificate processing. For golang#41147. Fixes golang#56672. Change-Id: I4c6bcb1b137a200dfe70cebc605ae57f49871184 Reviewed-on: https://go-review.googlesource.com/c/go/+/447655 Run-TryBot: Russ Cox <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Auto-Submit: Russ Cox <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/go/+/449016
No branches or pull requests
@rsc requested issue #41147 to be considered for backport to the next 1.19 minor release.
The text was updated successfully, but these errors were encountered: