On the recordRead 10 Oct 202619 facts
Signo
On the record
- API access
- API clients, called signees, can be assigned access to individual signing engines, and API requests are HMAC signed.github.com · read 4 Oct 2026
- API authentication
- API requests are HMAC signed.github.com · read 10 Oct 2026
- Databases
- Configuration supports either MySQL or SQLite.github.com · read 10 Oct 2026
- Distribution
- The project says Signo is available through NPM or Docker Hub, with NPM described as the simplest installation route.github.com · read 4 Oct 2026
- File signing
- It signs files through an HTTP API and supports plain signatures and Authenticode signing for Windows executables.github.com · read 4 Oct 2026
- Installation
- The README offers installation through NPM or Docker Hub and describes a Linux setup requiring Node.js 16 or 18.github.com · read 10 Oct 2026
- Integrations
- The README names YubiKey as a hardware-token example and points to a separate signo-client NPM package for API use.github.com · read 10 Oct 2026
- Intended use
- The project aims to let CI applications generate signed executables using certificates stored on hardware tokens.github.com · read 4 Oct 2026
- License
- The repository identifies the project as GPL-3.0 licensed.github.com · read 10 Oct 2026
- PKCS#11
- Signo supports PKCS#11 tokens and is intended to help CI applications use hardware-stored code-signing certificates.github.com · read 10 Oct 2026
- Planned features
- The README lists a cryptographically verifiable operation log, PDF signing, key and CSR generation, and importing certificates to tokens as planned features.github.com · read 10 Oct 2026
- Purpose
- Signo is an open source, self-hosted signing service that signs files through an HTTP API.github.com · read 10 Oct 2026
- Runtime requirement
- The quick start calls for a Linux machine with NodeJS 16 or 18 installed.github.com · read 4 Oct 2026
- Security setup
- The setup instructions require configuring an SSL certificate and listing PKCS#11 modules.github.com · read 4 Oct 2026
- Signature types
- It supports plain signing, which returns a binary signature, and Authenticode signing for Windows executables.github.com · read 10 Oct 2026
- Signing permissions
- Administrators can enable specific signing engines for each signee, which represents an API client.github.com · read 10 Oct 2026
- Token controls
- The service lists detected tokens and their keys and certificates; a token must be activated by entering its PIN before it can sign.github.com · read 10 Oct 2026
- Transport security
- The setup instructions require an SSL certificate for the HTTPS service, and say a self-signed certificate can be used if the infrastructure trusts it.github.com · read 10 Oct 2026
