Andreas Auernhammer c1a49be639 use crypto/sha256 for FIPS 140-2 compliance (#11623) ... This commit replaces the usage of github.com/minio/sha256-simd with crypto/sha256 of the standard library in all non-performance critical paths. This is necessary for FIPS 140-2 compliance which requires that all crypto. primitives are implemented by a FIPS-validated module. Go can use the Google FIPS module. The boringcrypto branch of the Go standard library uses the BoringSSL FIPS module to implement crypto. primitives like AES or SHA256. We only keep github.com/minio/sha256-simd when computing the content-SHA256 of an object. Therefore, this commit relies on a build tag `fips`. When MinIO is compiled without the `fips` flag it will use github.com/minio/sha256-simd. When MinIO is compiled with the fips flag (go build --tags "fips") then MinIO uses crypto/sha256 to compute the content-SHA256.		2021-02-24 09:00:15 -08:00
..
errors.go	add comment on exported error	2020-05-15 18:17:54 -07:00
reader_test.go	pkg/etag: add new package for S3 ETag handling (#11577)	2021-02-23 12:31:53 -08:00
reader.go	use crypto/sha256 for FIPS 140-2 compliance (#11623)	2021-02-24 09:00:15 -08:00
sha256_fips.go	use crypto/sha256 for FIPS 140-2 compliance (#11623)	2021-02-24 09:00:15 -08:00
sha256_nofips.go	use crypto/sha256 for FIPS 140-2 compliance (#11623)	2021-02-24 09:00:15 -08:00