You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
mateusz834
changed the title
crypto/x509: decide about marshalling of Policies/PolicyIdentifier
crypto/x509: decide about marshalling of Policies/PolicyIdentifiers
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 modulex
imports moduley
,y
usesPolicyIdentifiers
, thus makingx
unable to change the go directive, because it will causey
to break.CC @rolandshoemaker @golang/security
The text was updated successfully, but these errors were encountered: