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 when SIGSUM_POLICY_DIR is 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