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/x509: decide about marshalling of Policies/PolicyIdentifiers #67620

Open
mateusz834 opened this issue May 23, 2024 · 0 comments
Open

crypto/x509: decide about marshalling of Policies/PolicyIdentifiers #67620

mateusz834 opened this issue May 23, 2024 · 0 comments
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@mateusz834
Copy link
Member

mateusz834 commented May 23, 2024

In #64248 we decided that x509marshalpolicies would change the default from 0 to 1 in the go 1.23 release, currently we are in the release freeze, do we want to make this change at this point or should we wait till the 1.24 tree reopens?

Also before making such change i would like to make sure that we are all fine with breaking all code that currently only sets the PolicyIdentifiers field. There might be a case that module x imports module y, y uses PolicyIdentifiers, thus making x unable to change the go directive, because it will cause y to break.

CC @rolandshoemaker @golang/security

@mateusz834 mateusz834 added the NeedsFix The path to resolution is known, but the work has not been done. label May 23, 2024
@mateusz834 mateusz834 added this to the Go1.24 milestone May 23, 2024
@mateusz834 mateusz834 changed the title crypto/x509: decide about marshalling of Policies/PolicyIdentifier crypto/x509: decide about marshalling of Policies/PolicyIdentifiers May 23, 2024
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.
Projects
None yet
Development

No branches or pull requests

1 participant