minio/.github
Andreas Auernhammer 1d50cae43d
remove support for FIPS 140-2 with boringcrypto (#21292)
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>
2025-05-16 07:27:42 -07:00
..
ISSUE_TEMPLATE Add Subnet link in the issue template for urgency clause (#14131) 2022-01-20 09:37:40 -08:00
workflows remove support for FIPS 140-2 with boringcrypto (#21292) 2025-05-16 07:27:42 -07:00
ISSUE_TEMPLATE.md Slight tweaks to SUBNET portion of the template (#14205) 2022-01-28 16:04:16 -08:00
PULL_REQUEST_TEMPLATE.md small fix for the PR template (#18443) 2023-11-14 09:29:11 -08:00
logo.svg Migrate config to KV data format (#8392) 2019-10-22 22:59:13 -07:00
stale.yml change to do-not-close 2022-01-23 20:36:59 -08:00