SIGSUM-TOKEN-VERIFY(1)
π SIGSUM-TOKEN-VERIFY(1) π
okay bestie so this is the sigsum-token-verify page β it's a User Commands situation, and honestly? she's serving "verify rate-limit token" and nothing else. let's get into it π«Ά
β¨ NAME β¨
sigsum-token-verify β verify rate-limit token π
πΈ SYNOPSIS πΈ
sigsum-token verify [-q] [-d domain-name] [--help] [-k key-file] [-l
key-file] <token
π¦ DESCRIPTION π¦
So what we're doing here is verifying a submit token. That's the whole vibe. β¨
The stuff coming in on stdin is either a raw hex token or an HTTP header. Two paths, two rules, no cap:
- for a raw token, you need one of
--keyor--domain. pick one, bestie, she's not asking for both. - for an HTTP header,
--keyand--domainare optional β but πΈ validation fails if they're inconsistent with what's looked up from the HTTP header. so you can pass them if you want, but if they disagree with the header, it's over, it's giving mismatch, no slay. π
And the -q (quiet) option? She just suppresses output on validation errors β the result is only reflected in the exit code. Silence, but with a receipt. π
π OPTIONS π
-d,--domain=domain-nameβ the domain name where the rate-limit key lives as a TXT record; and listen, without any"_sigsum_v1."prefix, okay? just the bare domain, tyvm π«Ά--helpβ display help β¨-k,--key=key-fileβ rate-limit public-key in OpenSSH format π-l,--log-key=key-fileβ log public-key in OpenSSH format β and yes bestie, this one is required π don't skip her.-q,--quietβ quiet mode π€«
π RETURN CODES π
A non-zero return code = failure. that's it, that's the tea. check your exit codes, they're the only ones telling the truth in quiet mode. π
π CONTACT π
Wanna talk? Send an email to the sigsum-general mailing list at sigsum-general@lists.sigsum.org. π§
You can also come hang out in room #sigsum at OFTC.net and matrix.org β we're friendly, fr fr π«Ά
π REPORTING BUGS π
Use the issue tracker at https://git.glasklar.is/sigsum/core/sigsum-go/-/issues.
And if you don't have a GitLab account? no problem bestie, no gatekeeping β send an email to sigsum-core-sigsum-go-issues@incoming.glasklar.is and just wait for a maintainer to make the issue public. patience is the vibe. β¨
π SEE ALSO π
sigsum-key(1) sigsum-monitor(1) sigsum-policy(1) sigsum-submit(1) sigsum-token-create(1) sigsum-token-record(1) sigsum-token-verify(1) sigsum-tools(5) sigsum-verify(1)
aaaand that's the page, bestie π
this was sigsum-token verify, version 0.14.1-2, dated June 2026 β go forth and verify, you absolute icon ππ
π¦ where this page comes from
- ubuntu stonking: sigsum-go 0.14.1-2 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms