Update code signing with latest Azure Trusted Signing tools/tasks #1644
Conversation
This file contains 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
Use the new azure/trusted-signing-action in place of the now deprecated azure/azure-code-signing-action. https://github.com/azure/azure-code-signing-action https://github.com/azure/trusted-signing-action
Use our customised version of the dotnet/sign tool for Trusted Signing, including export of the certificate.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Update to the latest version of the GitHub Action (the
azure/azure-code-signing-actionaction has been replaced by theazure/trusted-signing-actionone).Deploy a forked version of the
Sign.Clitool for Trusted Signing, which includes the ability to export the certificate. The fork can be found here https://github.com/mjcheetham/sign/tree/export-opt, and the PR to submit this change upstream here Add option to download/export certificates from Trusted Signing dotnet/sign#734.With these changes we are now completely secret/credential free, and rely on federation only.