Skip to content
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

Automatically handle DeveloperID certificates. #1

Merged
merged 1 commit into from
Dec 6, 2021

Conversation

toonetown
Copy link

Rather than keying off the "ACTION" environment variable, we can key off the fact that it is a DeveloperID certificate - which causes the binary to be signed with a different Designated Requirement. Previously, the Developer ID designated requirement was used only when ACTION was set to "install". This change keys off of the certificate CN, and if it is a Developer ID certificate, it will generate the strings appropriate for that signature.

Rather than keying off the "ACTION" environment variable, we can key off the fact that it is a DeveloperID certificate - which causes the binary to be signed with a different Designated Requirement.  Previously, the Developer ID designated requirement was used only when ACTION was set to "install".  This change keys off of the certificate CN, and if it is a Developer ID certificate, it will generate the strings appropriate for that signature.
@chipjarred
Copy link
Owner

For some reason I didn't get a notification that you had already submitted this. Thank you. On first glance it looks good. Before I merge it though, I want to go through it one more time, and also check to see if anything needs to be updated in the Scripts/README.md file.

@chipjarred chipjarred merged commit 8f92f50 into chipjarred:master Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants