Publish the certificate thumbprints for DigiCert Federal SSP Intermediate CA - G6 - #2085
Open
arpitjain099 wants to merge 1 commit into
Open
arpitjain099 wants to merge 1 commit into
arpitjain099 wants to merge 1 commit into
Conversation
…iate CA - G6 The SHA-1 and SHA-256 values in that row are hashes of the PEM file rather than of the certificate. The shipped .cer parses to thumbprints 0dd44fd015c1f76327be46661456ce8f6fb346ec and 72653e7e6aa246b778a07592b4cf09e2b4f629e45994e289090f84d5c054686e. Of the PEM certificates under _implement/certs, this is the only row that publishes the file hash; the rest publish the thumbprint. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "DigiCert Federal SSP Intermediate CA - G6" row on the Distribute FCPCA page publishes hashes of the PEM file rather than thumbprints of the certificate.
Taking the
.certhe row links to and hashing it both ways:The second pair is what the page currently shows. The file is PEM, so the two differ.
The convention on the page is the thumbprint: of the PEM certificates under
_implement/certs, three publish the certificate thumbprint and this row is the only one that does not. The certificate itself is fine, its serial and validity match the rest of the row, so it is the table that is off.An admin comparing what Windows shows against this page sees a mismatch on a genuine certificate. It fails safe, since the reaction is to decline, but the page is what they are checking against.