---
name: "sigsum-verify"
section: "1"
platform: "linux"
package: "sigsum-go"
version: "0.11.2-1+b3"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/sigsum-verify"
---

# sigsum-verify(1)

enforce public logging

## NAME

sigsum-verify - enforce public logging

## SYNOPSIS

**sigsum-verify** \[*-v*\] \[*--help*\] \[*-k key-file*\] \[*-p policy-file*\] \[*--raw-hash*\] *proof-file \< input*

## DESCRIPTION

Verify that a message's signed checksum is logged for a given trust policy.  The message to be verified is read on stdin.

## OPTIONS

- **--help**

  Show usage message and exit

**-k**, **--key**=*key-file*

-

  Submitter public keys, one per line in OpenSSH format (required)

**-p**, **--policy**=*policy-file*

-

  Trust policy defining logs, witnesses, and a quorum rule (required)

- **--raw-hash**

  Input has already been hashed and formatted as 32 octets or a hex string

- **-v**, **--version**

  Show software version and exit

## RETURN CODES

A non-zero return code is used to indicate failure.

## CONTACT

Send an email to the sigsum-general mailing list at **sigsum-general@lists.sigsum.org.** You can also reach out in room **#sigsum** at **OFTC.net** and **matrix.org.**

## REPORTING BUGS

Use the issue tracker located at **https://git.glasklar.is/sigsum/core/sigsum-go/-/issues.** To file issues without a GitLab account, send an email to **sigsum-core-sigsum-go-issues@incoming.glasklar.is** and wait for a maintainer to make the issue public.

## SEE ALSO

[**sigsum-key**(1)](/sigsum-key/1.md) [**sigsum-monitor**(1)](/sigsum-monitor/1.md) [**sigsum-submit**(1)](/sigsum-submit/1.md) [**sigsum-token**(1)](/sigsum-token/1.md) **sigsum-tools**(5)