Aujas Automated Code Signing Platform vs OpenPubkey

Aujas Automated Code Signing Platform, or CodeSign, manages signing requests across software build and release processes. It routes approvals for projects, builds, and certificates, and records approval and file-signing activity. Signing keys and certificates can be held in an HSM or secure keystore, with access limited to authorized users and machines for approved requests. The platform supports signing through command-line integration, including parallel submissions, and can be included in DevOps pipelines. Listed options include basic, GPG, hash, force, append, MAGE, and WHQL signing; a malware scanner can inspect files before signing. Certificate support includes self-signed, standard certificates from any CA, and Extended Validation certificates. Aujas lists more than 50 supported file types, with plugins to add types, and support for Windows, Linux, and macOS. Deployment choices include a customer data center, public cloud, and managed cloud hosting. CodeSign is paid, with pricing on request; Aujas offers a scheduled demo covering platform features, architecture, and application flow.

OpenPubkey binds a user or workload identity established through OpenID Connect to a public key, so the identity can sign messages or artifacts. A PK Token represents control of an OIDC identity and its related private key at a particular time, provided the verifier trusts the identity provider. The project lists Google, Azure/Microsoft, Okta, OneLogin and Keycloak as compatible without changes to those providers; however, its client and verifier currently create and verify tokens from Google for users and GitHub for workloads. Current workload identity use requires GQ signatures. For user identity, they are unnecessary when the PK Token is not public. GQ signatures allow the identity provider’s signature to be stripped from an ID Token while preserving proof of that signature, preventing use against OIDC resource providers. OpenPubkey says it needs no additional certificate authority because the OpenID Provider fulfills that role. Public PK Tokens can reveal claims from an OIDC ID Token, potentially including a name or email address. The project is free under the Apache 2.0 license and is a Linux Foundation project; its repository says it is being prepared for version 1.0. The project directs technical questions to GitHub issues and offers a community Slack channel.