GODRIVER-4211ClosedWon't Do

Driver panics during TLS connection setup when GODEBUG=fips140=only because OCSP request creation uses SHA-1

h3. Detailed steps to reproduce the problem? When an application runs with {*}GODEBUG=fips140=only{*}, opening a TLS connection with certificate verification enabled crashes the process with a panic during OCSP verification. x/mongo/driver/ocsp/config.go:58 builds the OCSP request with no request options:     With nil options, golang.org/x/crypto/ocsp.CreateRequest falls back to crypto.SHA1 for the CertID hashes. In FIPS 140-only mode, Go's crypto/sha1 returns an error from Write,

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
OCSP
Labels
Tags and classification

No labels assigned.