Skip to content
Open core software, built in Singapore Established 2018  /  Five utilities
Jering
Talk to us

Code Signing

DevOps.AzurePipelines Jering documentation Open source Pipeline templates
Documentation menu

Code signing gives a package or an assembly a verifiable publisher identity. It is a supply chain decision, not a checkbox at the end of the pipeline.

What it protects

A signature lets a consumer check that the artifact came from the expected publisher and that it has not been altered since signing. The value depends on protecting the signing key and on a consumer that actually verifies it.

In the pipeline

Keep signing material in a secret store and expose it to the signing step only. Sign after the artifact is final. Do not sign a package and then modify it, because the modification invalidates the signature.

Scope

Not every project needs signing on day one. Decide based on who consumes the package and what the distribution channel requires. Document the decision either way.

Reference shelf