crypto: upgrade to BoringCrypto fips-20220613 and enable TLS 1.3 [freeze exception]

[FiloSottile]

Per the discussion at #62372 (comment), we decided to upgrade to BoringCrypto fips-20220613 and enable TLS 1.3.

Since the NIST SP 800-52 Rev. 2 deadline is January 1st, we need this in Go 1.22.

This only affects GOEXPERIMENT=boringcrypto.

[FiloSottile]

@gopherbot please open backport issues. All supported Go versions need to be able to comply with NIST SP 800-52 Rev. 2 in GOEXPERIMENT=boringcrypto mode.

/cc @golang/release @golang/security @rsc

[gopherbot]

Backport issue(s) opened: #64718 (for 1.20), #64719 (for 1.21).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

[gopherbot]

Change https://go.dev/cl/549695 mentions this issue: crypto/internal/boring: upgrade module to fips-20220613

[gopherbot]

Change https://go.dev/cl/549975 mentions this issue: crypto/tls: align FIPS-only mode with BoringSSL policy

[dmitshur]

Thanks for letting us know. The freeze exception bit here is approved.

[gopherbot]

Change https://go.dev/cl/553856 mentions this issue: [release-branch.go1.21] crypto/tls: align FIPS-only mode with BoringSSL policy

[gopherbot]

Change https://go.dev/cl/553855 mentions this issue: [release-branch.go1.21] crypto/internal/boring: upgrade module to fips-20220613

[gopherbot]

Change https://go.dev/cl/553875 mentions this issue: [release-branch.go1.20] crypto/internal/boring: upgrade module to fips-20220613

[gopherbot]

Change https://go.dev/cl/553876 mentions this issue: [release-branch.go1.20] crypto/tls: align FIPS-only mode with BoringSSL policy

[gopherbot]

Change https://go.dev/cl/558796 mentions this issue: Revert "crypto/internal/boring: upgrade module to fips-20220613" +1

[gopherbot]

Change https://go.dev/cl/558797 mentions this issue: [release-branch.go1.22] Revert "crypto/internal/boring: upgrade module to fips-20220613" +1

[gopherbot]

Change https://go.dev/cl/560275 mentions this issue: [release-branch.go1.21] Revert "crypto/internal/boring: upgrade module to fips-20220613" +1

[gopherbot]

Change https://go.dev/cl/560276 mentions this issue: [release-branch.go1.20] Revert "crypto/internal/boring: upgrade module to fips-20220613" +1

[gopherbot]

Change https://go.dev/cl/603375 mentions this issue: crypto/internal/boring: upgrade module to fips-20220613 / certificate 4735

[gopherbot]

Change https://go.dev/cl/603376 mentions this issue: crypto/tls: align FIPS-only mode with BoringSSL policy

[yhlee-tw]

@FiloSottile and @agl

when I checked the CMVP #4735, 2022061300 and the corresponding CAVP A2811, 2022061300, I couldn't find TLS 1.3 KDF listed (comparing with CAVP A4687, 2023042800 or CAVP A5370, 20240407

I am unsure whether the current CMVP #4735 covers the TLS 1.3 usage as I saw it was enabled in d363534 with 2022061300. (or maybe one of the newer versions is getting a cert soon, guessing from the module-in-progress)

(It's exciting to see #69536 coming)

[stevesmoot]

Looks like still lacks support here (https://go.googlesource.com/go/+/dev.boringcrypto/src/crypto/tls/handshake_server_tls13.go#47) any news?:
`
func (hs *serverHandshakeStateTLS13) handshake() error {

  | c := hs.c
  |  
  | if needFIPS() {
  | return errors.New("tls: internal error: TLS 1.3 reached in FIPS mode")
  | }
`

[rolandshoemaker]

@stevesmoot the dev.boringcrypto branch is deprecated and no longer used. You should be looking at master, where this check isn't present.

[stevesmoot]

awesome, thank you, clearly we werent tracking this closely enough.