Identify the artifacts you want to sign together
In SignPath, you define a project for each artifact, or a set of artifacts that should be signed in a single step. Typically, there is one set of artifacts per software product, development team or project. If you use continuous integration (CI) tools, the artifacts will be the output of a single build configuration, or a part of it. Or maybe you have several build configurations that create different versions of structurally identical artifacts – those can still be represented by a single SignPath project. (If you don’t use CI, we highly recommend starting now. A reproducible build process is a most basic ingredient for safe code signing.)
At the core of each SignPath project is an artifact configuration. It describes the file type of your artifact and a corresponding code signing method (e.g. an EXE file signed with Authenticode). You can also sign multiple files or complex nested artifacts, e.g.
- a ZIP archive containing several artifacts that need Authenticode signing
- a CAB file containing EXE and DLL files, all of which should be signed with Authenticode
- an MSI installer containing an Office add-in, which in turn contains DLLs – the MSI file and the DLLs should be signed using Authenticode, while the Office add-in has a ClickOnce manifest that requires manifest signing
For complex nested artifacts, creating the artifact configuration is a bit more involved. You need to create an XML file that describes the artifact, with all its nested elements, and the signing actions you want performed on these files. See Creating an artifact configuration.
Note that a tight configuration of your artifact reduces the risk of unwanted signatures. Add constraints liberally.
Create signing policies for each project
The same project is usually signed for different purposes, most commonly test- and release-signing. Define signing policies for each project as required.
|Signing Policy||Purpose||Certificate requirements||Signing requirements||Remarks|
||Limited to certain submitters (persons or CI)||Since the scope of the certificate is very limited and builds are frequent, manual approval is usually not required.|
|Release-signing||Signing software for
||Usually requires manual approval for each build||Release certificates are an attractive target. Be sure to review each signing request carefully before approval and don’t approve unexpected releases. Also, CI integration will help to make the entire build process more traceable.|
You might need more signing policies. For example, you might want to introduce an approval process for some submitters, but not for others. Or you might use different certificates for various kinds of builds. Define any number of signing policies to meet your organization’s requirements.
Last modified: 15. November 2018