-
Notifications
You must be signed in to change notification settings - Fork 28
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
Mention GODEBUG=fips140 in FIPS docs #1508
base: microsoft/main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this holds up to the claim that the doc describes all in-support versions of Go. Some comments about that, but I haven't gotten to the later parts of the doc yet.
@@ -42,7 +42,7 @@ The Microsoft Go fork provides several ways to configure the crypto backend and | |||
- [`GOEXPERIMENT` `allowcryptofallback`](#build-option-to-use-go-crypto-if-the-backend-compatibility-check-fails) | |||
- [`import _ "crypto/tls/fipsonly"` source change](#tls-with-fips-compliant-settings) | |||
- Runtime configuration: | |||
- [`GOFIPS` environment variable](#usage-runtime) | |||
- [`GODEBUG=fips140` setting](#usage-runtime) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think GOFIPS should still be mentioned here until it's no longer in a supported version of Microsoft Go. (At least, this list was intended to include everything.)
@@ -42,7 +42,7 @@ The Microsoft Go fork provides several ways to configure the crypto backend and | |||
- [`GOEXPERIMENT` `allowcryptofallback`](#build-option-to-use-go-crypto-if-the-backend-compatibility-check-fails) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line above this one (too far from a diff to comment directly) mentions requirefips
and should maybe also mention GOFIPS140=latest
.
The following sections describe how to enable FIPS mode and the effect of the `GODEBUG=fips140` setting on each supported platform. | ||
|
||
> [!NOTE] | ||
> Since Go 1.24, setting `GOFIPS=1` is equivalent to setting `GODEBUG=fips140=on`. The latter is the recommended way to enable FIPS mode. Support for the `GOFIPS` environment variable will be removed in Go 1.25. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this doesn't make it clear what GOFIPS=1
means in Go 1.23.
Co-authored-by: Davis Goodin <[email protected]>
For #1445.