Verify a receipt
Download the receipt from the Glacis portal, preserve the original file and use the supported offline glacis-verify tool supplied for your deployment.
Before you start
Section titled “Before you start”You need the original receipt, a verifier that supports its format, and trusted signing keys for the deployment. When checking witness evidence, obtain the corresponding proof material and trusted witness keys as well.
A key supplied only alongside an untrusted file is not enough to establish who signed it. Confirm the key’s provenance through your deployment’s supported distribution process.
Check the artifact
Section titled “Check the artifact”- Open the receipt in the portal and download its original artifact. Keep the original bytes and associated proof files together.
- Follow the offline verifier instructions supplied with your deployment.
- Read the verification result and which checks were performed. A successful signature check is distinct from completed witness, identity or content checks.
- Preserve the artifact, trusted key information, verifier version and result for the review.
Detailed commands and deployment-specific key instructions belong to the private handbook and the verifier’s supplied help.
If a check does not complete
Section titled “If a check does not complete”Missing keys, unsupported formats and unavailable proofs leave a check unresolved. Obtain the required material or compatible verifier before treating it as verified. If a signature or binding fails, preserve the artifact and result and contact Glacis through your agreed support channel.
Verification does not establish model correctness or complete traffic coverage. See Receipts and trust before using the result in an assurance claim.