Skip to content

Signing Tools

The Keyserver works with the signing tools your build already uses. Each tool keeps its own commands and output formats; only the signing step reaches the Keyserver. The tool sends a hash, and the Keyserver returns the signature under an approved operation, so the private key never reaches the build machine. This holds for KEYSTORE keys too: such a key leaves the Keyserver only through an explicit export, never through signing. Approvals, usage counts and the audit log apply as they do to a sign order sent through the REST API.

The tools connect in one of three ways:

  • PKCS#11 module (libpkcs11ks.so): OpenSSL, jarsigner, JSign, osslsigncode and the PKCS#11-enabled Cosign load it and see Keyserver keys as keys on a local token. See the PKCS#11 Library Reference.
  • CNG Key Storage Provider: signtool on Windows reaches Keyserver keys through it.
  • REST API sign order: stock Cosign signs a payload whose hash you submit as a normal sign order.

Every tool needs an access token and an approved operation, as REST signing does.


Files and firmware images

OpenSSL 3.x - PKCS#11: sign and verify arbitrary files, such as firmware images, with openssl through the PKCS#11 engine or provider. It produces a plain signature over the file, for verifiers on your devices or in your release process.

Java

jarsigner - PKCS#11: sign JAR files with the JDK's own jarsigner, through Java's SunPKCS11 provider. The result verifies with jarsigner -verify like any other signed JAR.

Windows executables

Authenticode - JSign, osslsigncode: Authenticode-sign EXE, DLL, MSI and other Windows files on Linux, macOS or Windows. JSign has the broadest format support; osslsigncode is a native binary that suits minimal CI images.

signtool - CNG KSP: Authenticode-sign with Microsoft's own signtool on a Windows build agent, with no JVM or OpenSSL engine.

Windows Development Signing Chain: build a ROOT key and an RSA signing key in the Keyserver and trust the root on your own Windows machines, to test Authenticode signing before you have a certificate from a public CA.

Containers and SBOMs

Container Images - Cosign: sign container images with Cosign, either with the official binary and a REST sign order, or in one command with a PKCS#11-enabled Cosign build. Both verify with stock Cosign.

SBOM Attestations - Cosign: bind a Software Bill of Materials to an artifact digest as a Cosign-verifiable attestation, without modifying the SBOM. For what the EU Cyber Resilience Act requires of SBOMs, see SBOMs and Supply-Chain Regulation.