[DNM] Test Azure Trusted Signing #249
Closed
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
Test the new setup for Azure Trusted Signing by signing the NuGet packages and the DLLs within.
martincostello
temporarily deployed
to
azure-trusted-signing
GitHub Actions
Inactive
|
Working as expected: 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Test the new setup for Azure Trusted Signing by signing the NuGet packages and the DLLs within.
Copied from Polly where I've previous setup Authenticode signing (but not with Trusted Signing).
There's no intention to actually use this here at this time as support for NuGet packages in Azure Trusted Signing is difficult at the moment due to a missing first-class integration with NuGet.org to associate the short-lived signing certificates with the publisher (reference).