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
90860e0 landed in master last week to fix #48674. The same issue affects all boring branches when crypto/tls/fipsonly is imported.
crypto/tls/fipsonly
@neild @FiloSottile could we have that fix backported into go1.16 and go1.17, and then cut the corresponding boring releases?
IMO this issue is sever enough to meet the backport policy, but I'm not sure if it also applies to boring branches.
The text was updated successfully, but these errors were encountered:
Seems worth backporting, opened #50585 and #50586.
Sorry, something went wrong.
No branches or pull requests
90860e0 landed in master last week to fix #48674. The same issue affects all boring branches when
crypto/tls/fipsonly
is imported.@neild @FiloSottile could we have that fix backported into go1.16 and go1.17, and then cut the corresponding boring releases?
IMO this issue is sever enough to meet the backport policy, but I'm not sure if it also applies to boring branches.
The text was updated successfully, but these errors were encountered: