-
Notifications
You must be signed in to change notification settings - Fork 453
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
Use the new signing certificate. #1312
Conversation
/azp run GitHub VFSForGit Mac Functional Tests |
No pipelines are associated with this pull request. |
/azp run GitHub VFSForGit Mac Functional Tests |
No pipelines are associated with this pull request. |
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.
How did you test this change or are you going to run the signing build to test it?
How did you know you should make this change? |
@kewillford I'll run a real-sign build once we're into a release branch. I'm reluctant to generate a signed build off a topic branch.
@wilbaker Owners of real-signed builds were instructed to move away from the SHA1 certs, and there is a table provided for which cert name to move to. I moved from |
The
Microsoft
certificate is a SHA1 certificate. Move to the hybrid certificate.