VERITROOPER — PACKAGE VERIFICATION
==================================================

This package is sealed with a standards-based digital signature covering every
delivered audit artifact (everything OUTSIDE this Integrity/ folder), linked to
VERITROOPER's canonical result hash.

WHAT EACH FILE IS
  Integrity/manifest.json   Lists every audit artifact + its SHA-256 (the signed payload).
  Integrity/manifest.p7s    Detached CMS/PKCS#7 signature over manifest.json's exact bytes.
  Integrity/signer_cert.pem The signer's certificate (public key). SELF-SIGNED — see TRUST below.
  Integrity/timestamp.tsr   RFC 3161 trusted timestamp (if present).
  Integrity/tsa_chain.pem   The timestamp authority's chain (trust its ROOT from your own store).

WHAT IS SIGNED / TIMESTAMPED
  The signature covers the exact bytes of Integrity/manifest.json.
  A trusted timestamp (Integrity/timestamp.tsr) applies to the SHA-256 digest of the
exact canonical Integrity/manifest.json bytes.
  Manifest SHA-256: e9777e8120512633f31f4dabe42b8e9e04745ed2ddc9782c389dfa16fb883b7a

VERIFY WITH THE BUNDLED TOOL
  vt-verify <this-folder>
  (add  --trust-fingerprint 5A:91:5B:25:B2:C3:25:FC:B1:32:97:20:CD:D8:78:E5:B7:C8:A7:76:B8:D2:72:0B:B1:87:89:2E:E3:E2:A5:D0  ONLY if you obtained that
   fingerprint through a trusted out-of-band channel — see TRUST below.)

VERIFY WITH STANDARD OPENSSL
  Signature:  openssl cms -verify -binary -inform DER -in Integrity/manifest.p7s \
                 -content Integrity/manifest.json -certfile Integrity/signer_cert.pem \
                 -noverify -out verified_manifest.json
  Timestamp:  openssl ts -verify -data Integrity/manifest.json \
                 -in Integrity/timestamp.tsr -CAfile <your-trusted-tsa-ca.pem>
  Then confirm each file's SHA-256 matches Integrity/manifest.json.

TRUST (IMPORTANT)
  The signer certificate is SELF-SIGNED. A valid signature proves the package was
  signed by the key whose certificate is included here and has not been altered
  since. It does NOT by itself prove the signer is Veritrooper LLC or your own
  organization. Establish that only by matching the signer fingerprint

      5A:91:5B:25:B2:C3:25:FC:B1:32:97:20:CD:D8:78:E5:B7:C8:A7:76:B8:D2:72:0B:B1:87:89:2E:E3:E2:A5:D0

  against a record you obtained SEPARATELY (pilot agreement, onboarding document,
  a signed email, or a published verification page). If it matches, the package
  came from that registered signer. If you have no such record, treat identity as
  UNVERIFIED even when the signature is mathematically valid.
