Wade Simmons 90c7630270 extract the internal FIPS GCM implementation ...

We do this because the TLS wrapper is not thread safe on Open. instead of locking around it we
can grab the internal implementation that is thread safe. This is the FIPS
module implementation: `crypto/internal/fips140/aes/gcm.GCMWithXORCounterNonce`

- https://github.com/golang/go/blob/go1.26.4/src/crypto/internal/fips140/aes/gcm/gcm_nonces.go#L212-L287

The wrapper is struct `crypto/tls.xorNonceAEAD`, with field `aead`:

- https://github.com/golang/go/blob/go1.26.4/src/crypto/tls/cipher_suites.go#L482-L487

This can be cleaned up once these FIPS implementations are exposed directly:

- https://github.com/golang/go/issues/73110

2026-07-08 10:19:48 -04:00

..

aesgcm.go

Remove the global noiseEndianness var (#1707)

2026-05-06 17:37:03 -05:00

boring_test.go

boringcrypto cleanup

2026-06-09 13:24:59 -04:00

boring.go

boringcrypto cleanup

2026-06-09 13:24:59 -04:00

chachapoly.go

Remove the global noiseEndianness var (#1707)

2026-05-06 17:37:03 -05:00

cipher_state_test.go

boringcrypto cleanup

2026-06-09 13:24:59 -04:00

cipher_state.go

WIP

2026-06-09 10:31:49 -04:00

fips140_test.go

extract the internal FIPS GCM implementation

2026-07-08 10:19:48 -04:00

fips140.go

extract the internal FIPS GCM implementation

2026-07-08 10:19:48 -04:00

fips140enforce.go

cleanup enforcement

2026-06-09 15:33:31 -04:00

nist.go

minor text fixes (#1135)

2024-05-03 20:43:40 -05:00

notboring.go

boringcrypto cleanup

2026-06-09 13:24:59 -04:00

pkcs11.go

add PKCS11 support (#1153)

2024-09-09 17:51:58 -04:00