go/doc/next
Filippo Valsorda 6114b69e0c crypto/tls: relax native FIPS 140-3 mode
We are going to stick to BoringSSL's policy for Go+BoringCrypto, but
when using the native FIPS 140-3 module we can allow Ed25519, ML-KEM,
and P-521.

NIST SP 800-52r2 is stricter, but it only applies to some entities, so
they can restrict the profile with Config.

Fixes #71757

Change-Id: I6a6a4656eb02e56d079f0a22f98212275a40a679
Reviewed-on: https://go-review.googlesource.com/c/go/+/650576
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Junyang Shao <shaojunyang@google.com>
Auto-Submit: Filippo Valsorda <filippo@golang.org>
Reviewed-by: Daniel McCarney <daniel@binaryparadox.net>
Reviewed-by: David Chase <drchase@google.com>
2025-03-13 13:33:22 -07:00
..
6-stdlib crypto/tls: relax native FIPS 140-3 mode 2025-03-13 13:33:22 -07:00
1-intro.md doc: initialize next directory for Go 1.25 2025-02-03 07:52:07 -08:00
2-language.md doc: initialize next directory for Go 1.25 2025-02-03 07:52:07 -08:00
3-tools.md doc/next: add release note for new toolchain line behavior 2025-03-13 08:02:03 -07:00
4-runtime.md internal/godebugs: add decoratemappings as an opaque godebug setting 2025-03-10 08:29:59 -07:00
5-toolchain.md doc/next: add tentative DWARF 5 release note fragment 2025-03-13 05:16:49 -07:00
7-ports.md doc: initialize next directory for Go 1.25 2025-02-03 07:52:07 -08:00