.png){kind=logo}
The following provides an overview of the SignServer capabilities and support, with relevant links to documentation and external standards.
SignServer supports multiple application servers and standard, high-performance databases. For more information on SignServer requirements, see Installation Prerequisites in the SignServer Software Stack documentation.
In This Section
A quick-reference overview of what can be signed, which Worker to use, and links to further documentation.
A list of HSMs supported in SignServer, based on deployment.
A list of databases supported in SignServer, based on deployment.
A high-level reference of the supported algorithms types and key specifications.
Native Signing Tools
Enterprise
Some build environments and packaging pipelines rely on native platform signing tools. SignServer supports integration with these tools, keeping signing keys centrally protected in the HSM while preserving the existing tool invocation in your build scripts.
The integration model depends on the tool:
-
Signum Agents expose a platform-native keystore interface (macOS Keychain or PKCS#11 token) backed by SignServer. Any tool that can sign through the OS keystore or a PKCS#11 module can use this path without modification. See Signum Agents.
-
SignWrapper-GPG is a drop-in replacement script for the
gpgbinary, intercepting calls from tools that use GPG for signing and forwarding them to SignServer through SignClient. See SignWrapper-GPG.
The underlying SignServer Worker handling the request is a Plain Signer for Signum Agent workflows or an OpenPGP Signer/OpenPGP Plain Signer for GPG-based workflows.
|
Tool |
Platform |
Integration mechanism |
SignServer component |
Guide |
|---|---|---|---|---|
|
|
macOS |
Signum Agent (virtual keystore) |
||
|
|
macOS |
Signum Agent (virtual keystore) |
||
|
|
Linux |
Signum Linux Agent (PKCS#11 module) |
||
|
|
Linux |
SignWrapper-GPG (drop-in |