Feature Request
azidentity is calling x/crypto/pkcs12 at
|
"golang.org/x/crypto/pkcs12" |
this is problematic for fips compliance and doesn't allow consumers to fully use the go 1.24 fips support because x/crypto is not covered (https://go.dev/doc/security/fips140)
Would it be possible to move loadPKCS12Cert to a separate file and use an empty implementation if a build tag is passed to avoid linking x/crypto in the final binary ?
Feature Request
azidentity is calling x/crypto/pkcs12 at
azure-sdk-for-go/sdk/azidentity/client_certificate_credential.go
Line 20 in 3f308de
this is problematic for fips compliance and doesn't allow consumers to fully use the go 1.24 fips support because x/crypto is not covered (https://go.dev/doc/security/fips140)
Would it be possible to move
loadPKCS12Certto a separate file and use an empty implementation if a build tag is passed to avoid linking x/crypto in the final binary ?