Documentation  ❯  Trusted Build Systems

• Abstract
• Configuration
• Available connectors
  • Build node authentication
  • Jenkins CI
  • AppVeyor

Available for Enterprise subscriptions

Abstract

Trusted build systems create a trust relationship between SignPath and certain systems used in your build pipeline. They are typically implemented as connectors and configured in SignPath. Use trusted build systems to provide origin metadata with your signing requests and enable origin verification.

Configuration

To add a trusted build system to your SignPath organization:

• go to the Trusted Build Systems page (top menu) and click Add.
• enter a name, slug and (optionally) description
• remember the token that is created as a result

The token must then be used to configure the connector (see connector documentation). You can now link this trusted build system to your projects.

To use a trusted build system in a project:

• open the project
• find the Trusted build systems section
• click Link
• select one of the trusted build systems of your organization
• depending on the type of build system, you might need to add authentication information and/or an artifact path (see your connector’s documentation)

The build system can now be used to submit signing requests with origin metadata. A trusted build system is required for signing policies with origin verification enabled.

Available connectors

Build node authentication

A connector is available that will let you use TLS client certificates for build node authentication.

This results in a two-fold authentication strategy:

• CI User: a project-specific token must be presented to submit a signing request (usually stored as a secret in the CI system’s project configuration)
• Build node: only specific build nodes are able to submit the signing request

This ensures that a CI User token cannot be used outside the CI system. It’s also possible to restrict its use to certain build nodes. We recommend defining groups of build nodes based on their security attributes. Ideally, build nodes authorized for release signing meet the following requirements:

• No direct access for development teams (file shares, RDP etc.)
• Administrative permissions limited to a small number of administrators
• Build scripts run without elevated permissions

If you need build nodes with wider permission sets, consider separating the process of compilation and packaging from other steps (e.g. running tests). You might also want to consider signing initial builds as release candidates, and only provide release signatures after testing.

You may configure the system to accept certificates based on

• subject/distinguished name conditions (e.g. common name or organizational unit)
• the issuer (e.g. issued by a certain immediate certificate)
• a Microsoft Certificate Server Template ID (useful if you assign certificates to Active Directory computer groups)

Contact support@signpath.io for the connector and documentation.

Jenkins CI

A connector is available that connects Jenkins CI as a Trusted Build System.

This connector ensures that

• A build was actually performed by a specific Jenkins CI instance, not by some other entity in possession of the CI User token
• Origin metadata is provided by Jenkins CI, not the build script, and can therefore not be forged
• The artifact is stored as an immutable Jenkins artifact before it is submitted for signing

Contact support@signpath.io for the connector and documentation.

AppVeyor

Prerequisites and restrictions

This feature is currently dedicated to Open Source projects. Future versions will allow disabling certain limitations in paid subscriptions.

Current limitations:

• The AppVeyor project and the Git repository must be public

In order to ensure Origin Verification, you cannot submit a signing request from an unfinished build. Instead, you have to finish the build job without signing, and then trigger a signing request with origin verification. When signing is completed, you can use a Webhook handler for further processing, such as uploading the signed artifact to a repository.

The following checks are performed:

• No additional scripts may be executed during the build step and no cache entries may be used (so that the build remains fully traceable and is only built from the repository). The scripts must be all set to off at the bottom of the project settings page on AppVeyor.
• The build settings may not be modified between starting the AppVeyor build and calling SignPath.io
• The build configuration must be stored in the root directory under the name appveyor.yml or .appveyor.yml (no custom name is allowed to be set under Project settings and Custom configuration .yml file name)

This is to ensure that the binary artifacts result purely from the specified source code.

Setup

This figure shows the secrets that must be shared between AppVeyor.com and SignPath.io:

deploy:
- provider: Webhook
  url: https://app.signpath.io/API/v1/<ORGANIZATION_ID>/Integrations/AppVeyor?ProjectSlug=<PROJECT_SLUG>&SigningPolicySlug=<SIGNING_POLICY_SLUG>
  authorization:
     secure: <ENCRYPTED_SIGNPATH_API_TOKEN>

Attached build documentation

SignPath adds the following information to packages:

• For NuGet packages:
  1. The build settings are stored in an AppVeyorSettings.json file in the root of the NuGet package
  2. The commit hash and repository URL are written to the metadata of the NuGet package

These steps allow consumers of the signed artifact to verify source code version and build settings.