-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
Quay Hosted
-
0
Based on reading KCS https://access.redhat.com/solutions/5216821
"DigiCert SHA2 High Assurance Server CA"
and the following output:
$ openssl s_client -connect quay.io:443 -servername quay.io
CONNECTED(00000003)
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA
verify return:1
depth=1 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
verify return:1
depth=0 C = US, ST = North Carolina, L = Raleigh, O = "Red Hat, Inc.", CN = *.quay.io
verify return:1
—
Certificate chain
0 s:C = US, ST = North Carolina, L = Raleigh, O = "Red Hat, Inc.", CN = *.quay.io
i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
1 s:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA
i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA
—
Signed Certificate Timestamp:
Timestamp : May 27 12:32:55.214 2020 GMT
Am I missing something or is Quay.io affected? It appears one of my client's proxy is already blocking quay.io.