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
..
message	Add audit log for decommissioning (#14858)	2022-05-04 00:45:27 -07:00
target	use crypto/sha256 only for FIPS 140-2 compliance (#14983)	2022-05-27 06:00:19 -07:00
audit.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
config.go	Make audit webhook and kafka config dynamic (#14390)	2022-02-24 09:05:33 -08:00
console.go	improve logs, fix banner formatting (#14456)	2022-03-03 13:21:16 -08:00
help.go	Add "enable" to config help (#14866)	2022-05-05 04:17:04 -07:00
legacy.go	feat: Add support for kakfa audit logger target (#12678)	2021-07-13 09:39:13 -07:00
logger.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
logonce.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
reqinfo.go	fix: audit log to support object names in multipleObjectNames() handler (#14017)	2022-01-03 01:28:52 -08:00
targets.go	Cancel old logger/audit targets outside lock (#14927)	2022-05-16 13:32:36 -07:00
utils.go	run gofumpt cleanup across code-base (#14015)	2022-01-02 09:15:06 -08:00