Sigillr
A seal you can check, with nothing personal behind it. Sigillr (Latin sigillum: seal, signet)
is a public identity registry. People and organisations register the public keys of their
certificates themselves, under a pseudonymous user_id. The site logs them in with that same
certificate (mutual TLS). Anyone can then look up a key or certificate and see which identity it is
bound to, whether it is still valid, and its whole history.
What it does
- Directory: pseudonymous identities, people and organisations, with the tags they choose.
- Key registry: which keys belong to which
user_id, and whether each is active, expired or revoked. - Identity provider: an OpenID Connect provider whose ID tokens carry only the issuer and the
user_id.
The source of truth is a repository of YAML records and public keys. Only the service writes to it and anyone can read it. The relational index is disposable and rebuilt from that repository.
No personal data
Sigillr holds no personally identifiable data: no email address, no profile photo, no legal name. A
user_id or pseudonym that looks like an email address, including obfuscated forms, is refused.
Values you publish stay in the public history permanently, and you are told so, and
acknowledge it, before anything is published.
What it is not
- It is not a certificate authority: it issues no certificates.
- It never stores private keys.
- It is not a credential platform or a wallet.
Sigillr is open-source software (MIT OR Apache-2.0) that anyone can run. The public instance is run
by provr at sigillr.provr.dev.
Status: the project is at its start. This guide describes what Sigillr is and will do; Running an instance says what the current build does.
Running an instance
Sigillr is written in Rust. This page covers what works today and what later releases add.
Install
Build from source with a recent stable Rust toolchain. Clone
https://github.com/startr-trade/sigillr, then from the checkout:
cargo build --release --locked
./target/release/sigillr --help
What later releases add
The current build is the workspace skeleton: it has the command-line entry point and nothing that serves requests yet. Later releases add, in order, the registry repository and index, mutual-TLS login and key registration, public verification, revocation checks (CRL and OCSP), and the OpenID Connect provider. Each release’s notes are under Release notes.
The settings an instance will take are listed in Configuration.
Publishing this guide
The guide is built with mdBook (make docs, or
mdbook build docs/guide) and published to GitHub Pages by .github/workflows/docs.yml. GitHub
Pages must be enabled once for the repository: Settings, Pages, Source “GitHub Actions”. That
switch belongs to the repository owner.
Configuration
Every setting below is planned: no code reads any of them yet. The table fixes the intended behaviour and defaults so that operators and later releases agree. It mirrors the architecture view of configuration; a value marked “open question” is not yet decided.
| Setting | Default | Status |
|---|---|---|
| accepted certificate issuers | open question | planned |
| registry repository location | none; required | planned |
| index database | none; required, disposable | planned |
| waiting window for recovery and disable requests | 48 hours | planned |
| authorisation code lifetime | 60 seconds, single use, PKCE (S256) required | planned |
| ID token lifetime | 5 minutes | planned |
| access token lifetime | 10 minutes, sender-constrained (RFC 8705 mTLS or RFC 9449 DPoP) | planned |
| refresh token | rotated on every use; idle limit 7 days; absolute limit 30 days, never past the login certificate’s expiry | planned |
| CA revocation re-check | at every login and every token refresh | planned |
| cached OCSP/CRL answer reuse | until its nextUpdate, at most 1 hour; no fresh answer means refusal | planned |
The token values follow the OAuth 2.0 Security Best Current Practice (RFC 9700). The index database can be deleted at any time: it is rebuilt from the registry repository.
Release notes
One page per release, named for its version (for example 0.1.0.md), is added here when the
release is cut. There is no release yet.