SIGSUM-MONITOR(1)
π sigsum-monitor(1) β the manual page, but make it make sense
okay bestie, welcome to the sigsum-monitor page from the User Commands section π this is the tool that goes and discovers signed checksums for you, and I'm about to explain the whole thing with zero gatekeeping.
β¨ NAME β¨
sigsum-monitor β discover signed checksums for one or more keys π¦
πΈ SYNOPSIS πΈ
sigsum-monitor [-v] [--diagnostics log-level] [--help] [-i interval] [-P
policy-name] [-p policy-file] key-files
π DESCRIPTION π
So basically: it discovers signed checksums for public keys in OpenSSH format. That's the whole vibe.
β οΈ be warned though, bestie β this is a work-in-progress implementation. Witness cosignatures are not verified and no state is kept between runs. So like, it's giving "iconic but still cooking". π
π OPTIONS π
--diagnostics=log-levelβ sets the log level. Available levels:fatal,error,warning,info,debug. Default is[info]. π--helpβ shows the usage message and dips out. bye! π-i,--interval=intervalβ how often to fetch the latest entries. Default is[10m0s]. β°-P,--named-policy=policy-nameβ use a named trust policy that defines the logs, the witnesses, and the end-user's quorum rule. π₯-p,--policy=policy-fileβ use a trust policy file that defines the logs, the witnesses, and the end-user's quorum rule. (yes, it's the file version of-P, they're the same energy but one is a name and one is a path, iykyk) π«Ά-v,--versionβ shows the program version and exits. β¨
π RETURN CODES π
A non-zero return code means failure. That's it, that's the rule. no cap.
π«Ά CONTACT π«Ά
Wanna talk to a real human about this? Send an email to the sigsum-general mailing list at sigsum-general@lists.sigsum.org. π
You can also come hang out in room #sigsum on OFTC.net and matrix.org. we don't bite π§
π¦ ENVIRONMENT π¦
The behavior of the sigsum tools is affected by these environment variables, bestie:
SIGSUM_POLICY_DIRβ if it's set, this decides where the sigsum tools go looking for named policy files (*.sigsum-policy). π
π FILES π
/etc/sigsum/policyβ this directory is the default location for named policy files (*.sigsum-policy), for whenSIGSUM_POLICY_DIRis not set. it's the fallback queen πΈ
π REPORTING BUGS π
Found a bug? (iconic of you tbh) Use the issue tracker right here:
https://git.glasklar.is/sigsum/core/sigsum-go/-/issues
And if you wanna file issues without a GitLab account? Totally fine, just send an email to sigsum-core-sigsum-go-issues@incoming.glasklar.is and then wait for a maintainer to make the issue public. patience is a virtue fr fr β
π SEE ALSO π
sigsum-key(1) sigsum-policy(1) sigsum-submit(1) sigsum-token(1) sigsum-tools(5) sigsum-verify(1)
go read those too, they're all part of the family π
okay that's the whole page, you ate that. β¨ This was sigsum-monitor version 0.14.1-2, dated June 2026. take care of her, she's doing her best π
ππ
π¦ 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