mirror of https://github.com/minio/minio.git
This commit removes FIPS 140-2 related code for the following reasons: - FIPS 140-2 is a compliance, not a security requirement. Being FIPS 140-2 compliant has no security implication on its own. From a tech. perspetive, a FIPS 140-2 compliant implementation is not necessarily secure and a non-FIPS 140-2 compliant implementation is not necessarily insecure. It depends on the concret design and crypto primitives/constructions used. - The boringcrypto branch used to achieve FIPS 140-2 compliance was never officially supported by the Go team and is now in maintainance mode. It is replaced by a built-in FIPS 140-3 module. It will be removed eventually. Ref: https://github.com/golang/go/issues/69536 - FIPS 140-2 modules are no longer re-certified after Sep. 2026. Ref: https://csrc.nist.gov/projects/cryptographic-module-validation-program Signed-off-by: Andreas Auernhammer <github@aead.dev> |
||
---|---|---|
.. | ||
api | ||
batch | ||
browser | ||
callhome | ||
compress | ||
dns | ||
drive | ||
etcd | ||
heal | ||
identity | ||
ilm | ||
lambda | ||
notify | ||
policy | ||
scanner | ||
storageclass | ||
subnet | ||
bool-flag.go | ||
bool-flag_test.go | ||
certs.go | ||
certs_test.go | ||
certsinfo.go | ||
config.go | ||
config_test.go | ||
constants.go | ||
crypto.go | ||
crypto_test.go | ||
errors-utils.go | ||
errors.go | ||
help.go | ||
legacy.go | ||
server.go |