-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: migrate to a CA issued certificate #5893
feat: migrate to a CA issued certificate #5893
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
signature is ok but hash is different for me
> sha256sum contrib/windeploy/win-codesign.cert
5dcc037bb56205a8744c99d1ba15e8fc7e64144ba3ce728ce57546d804469ea1 contrib/windeploy/win-codesign.cert
Very odd... Here is the diff between the two files; they appear the same to me; maybe some metadata difference or something?
Anyhow; after comparing the two files are the same based on this x509 output
so here is a sig on both hashes as they both appear correct
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
hashes matched, pgp signatures is pasta's indeed.
$ openssl x509 -in contrib/windeploy/win-codesign.cert -text
...
Not Before: Feb 21 00:00:00 2024 GMT
Not After : Feb 21 23:59:59 2027 GMT
...
Subject: C = US, ST = Arizona, L = Mesa, O = "Dash Core Group, Inc.", CN = "Dash Core Group, Inc."
seems as cert is valid too, though I don't know how to test it.
0c8b2d9
to
3758950
Compare
Issue being fixed or feature implemented
Uses a new CA issued certificate
What was done?
Certificate changed; the issuer according to the certificate is
GoGetSSL G4 CS RSA4096 SHA256 2022 CA-11
In reality, the CA is digicert and the root CA isDigiCert Trusted Root G4
and is issued to "Dash Core Group, Inc."How Has This Been Tested?
Signed a binary with it see: https://www.virustotal.com/gui/file/a6577f3b8b474cfb1def1ea339795cb229b26d248d71f0b6f0b65e9e9ba3411b/details. I can share the binary if you'd like.
Breaking Changes
Not really any; unless someone is relying on a specific certificate.
Signature
Checklist:
Go over all the following points, and put an
x
in all the boxes that apply.