Loading...

XML

Word

Printable

Type: Feature
Resolution: Duplicate
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: config-tool, quay, quay-builder
Labels:

Hierarchy Progress:
0
Hierarchy Progress Bar:

0% 0%

RICE Score:
0

SFDC Cases Links:
SFDC Cases Counter:

Since all regulated customers in the US require FIPS 140-3 compliance (no waivers anymore) and we position Quay for security / governance focused customers we should become FIPS certified similar to what we're working on for OpenShift in parallel. Some background on FIPS here: https://mojo.redhat.com/groups/products-and-technologies/blog/2019/06/25/what-is-fips-and-why-should-i-care

is incorporated by

PROJQUAY-1546 Quay and Clair become FIPS 140-3 compliant

New

relates to

PROJQUAY-1340 Quay runs fine on top of an FIPS-enabled OpenShift Cluster

Closed

PROJQUAY-649 "openssl passwd" incorrect on OCP4 with FIPS mode enabled

Closed

PROJQUAY-224 Switch to python-cryptography completely

Closed

Assignee:: Bill Dettelback

Reporter:: Dirk Herrmann (Inactive)

Votes:: 40 Vote for this issue

Watchers:: 29 Start watching this issue

Created:: 2018/09/24 3:43 PM

Updated:: 2024/03/25 6:36 PM

Resolved:: 2021/11/12 5:44 PM