Update Windows signing certificate hash #5300
Merged
Conversation
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
The Git LFS signing certificate for Windows binaries has changed, so we update the default signing certificate SHA-1 hash in the Makefile. (The last update was in commit 16eec17 of PR git-lfs#4946 in 2022.) The commands used to generate this hash were: openssl pkcs12 -info -in codesign.pfx -out codesign.pem openssl x509 -text -in codesign.pem -fingerprint | \ grep Fingerprint | sed 's/^SHA1 Fingerprint=//' | \ sed 's/://g' | tr [:upper:] [:lower:]
Member
Author
|
Just FYI to @git-lfs/core reviewers -- the failing Windows CI check in |
bk2204
approved these changes
Mar 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 Git LFS signing certificate for Windows binaries has changed, so we update the default signing certificate SHA-1 hash in the Makefile.
(The last update was in commit 16eec17 of PR #4946 in 2022.)
The commands used to generate this hash were: