Skip to content

Commit 1ab36a4

Browse files
Update README.md
1 parent 3384cf1 commit 1ab36a4

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
1-
# CodeSigningDemo
2-
Skeleton for demonstrating use of the Sign CLI tool
1+
# Sign CLI CI sample workflows
2+
3+
Code signing is a complex process that may involve multiple signing formats and artifact types. Some artifacts are containers that contain other signable file types. For example, NuGet Packages (`.nupkg`) frequently contain `.dll` files. The signing tool will sign all files inside-out, starting with the most nested files and then the outer files, ensuring everything is signed in the correct order.
4+
5+
Signing `.exe`/`.dll` files, and other Authenticode file types is only possible on Windows at this time. The recommended solution is to use a multi-stage/job build where the signing steps run on Windows. Running code signing on a separate stage to ensure secrets aren't exposed to the build stage.
36

47
## Azure Setup
58

@@ -19,7 +22,7 @@ The following variables are used by the signing build:
1922
- `Client Secret` for Azure DevOps Pipelines
2023
- `Subscription Id` for GitHub Actions
2124

22-
### Azure DevOpps Pipelines
25+
### Azure DevOps Pipelines
2326

2427
The `azure-pipelines.yml` shows how you can use a multi-stage build with code signing for Azure DevOps
2528

0 commit comments

Comments
 (0)