minio/internal/crypto
Harshavardhana 9d07cde385
use crypto/sha256 only for FIPS 140-2 compliance (#14983)
It would seem like the PR #11623 had chewed more
than it wanted to, non-fips build shouldn't really
be forced to use slower crypto/sha256 even for
presumed "non-performance" codepaths. In MinIO
there are really no "non-performance" codepaths.
This assumption seems to have had an adverse
effect in certain areas of CPU usage.

This PR ensures that we stick to sha256-simd
on all non-FIPS builds, our most common build
to ensure we get the best out of the CPU at
any given point in time.
2022-05-27 06:00:19 -07:00
..
auto-encryption.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
doc.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
error.go run gofumpt cleanup across code-base (#14015) 2022-01-02 09:15:06 -08:00
header.go run gofumpt cleanup across code-base (#14015) 2022-01-02 09:15:06 -08:00
header_test.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
key.go use crypto/sha256 only for FIPS 140-2 compliance (#14983) 2022-05-27 06:00:19 -07:00
key_test.go add gocritic/ruleguard checks back again, cleanup code. (#13665) 2021-11-16 09:28:29 -08:00
metadata.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
metadata_test.go run gofumpt cleanup across code-base (#14015) 2022-01-02 09:15:06 -08:00
sse-c.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
sse-kms.go do not crash when KMS is not enabled (#14634) 2022-03-27 08:54:01 -07:00
sse-s3.go listing: improve listing of encrypted objects (#14667) 2022-04-04 11:42:03 -07:00
sse.go run gofumpt cleanup across code-base (#14015) 2022-01-02 09:15:06 -08:00
sse_test.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00