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

crypto/tls: add GODEBUG to control max RSA key size #61965

Closed
rolandshoemaker opened this issue Aug 11, 2023 · 5 comments
Closed

crypto/tls: add GODEBUG to control max RSA key size #61965

rolandshoemaker opened this issue Aug 11, 2023 · 5 comments
Labels
NeedsFix The path to resolution is known, but the work has not been done. Security
Milestone

Comments

@rolandshoemaker
Copy link
Member

tlsmaxrsasize, See http://go.dev/cl/517495.

@rolandshoemaker
Copy link
Member Author

@gopherbot please open backport issues.

@gopherbot
Copy link

Backport issue(s) opened: #61966 (for 1.20), #61967 (for 1.21).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

@mknyszek mknyszek added Security NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Aug 11, 2023
@mknyszek mknyszek added this to the Backlog milestone Aug 11, 2023
@dmitshur dmitshur modified the milestones: Backlog, Go1.22 Aug 11, 2023
@dmitshur
Copy link
Contributor

CL 517495 is submitted. Is there more to do for Go1.22?

@rolandshoemaker
Copy link
Member Author

I don't believe so, I opened this after the fact in order to create backport issues, so it didn't get closed when the CL was submitted (because it was submitted before the issue existed 😅). Can probably be closed.

@dmitshur
Copy link
Contributor

Let's close it to help keep issues that are open actionable, then. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsFix The path to resolution is known, but the work has not been done. Security
Projects
None yet
Development

No branches or pull requests

4 participants