How to verify this dossier

Azoth produced this dossier from a workspace’s sealed journal. You can check for yourself — without trusting Azoth, or the organisation that handed it to you — that it was not altered and that it existed on the date it states.

What it holds

the sealed decisions of a period, and how the law applicable to the workspace was covered.

Three steps

  1. Download the workspace’s public keys yourself, from Azoth and not from this dossier: /api/proof/keys/<workspace>. Open the offline verifier — the « azoth-verify.html » page (one page, which connects to nothing) or the « azoth-verify » command-line tool — and give it the ZIP file as you received it, with those keys (« --keys »).
  2. Read the verdict. The dossier is verified when every file matches its hash (manifest.json), the chain of decisions is intact and it is signed by one of the keys you gave. A dossier without a signature, or signed only by the key it ships itself, is not verified: anyone could have rebuilt it. Each check is listed, with what it found.
  3. Look at the date and the author. « anchor.tsr », when present, is the token of an independent time-stamping authority (RFC 3161): the dossier existed on that date. To trust it fully, give the verifier the root certificate that authority publishes (« --tsa-root »). « signature.jws » is the dossier signed with the workspace’s key; it also commits what the dossier covers — the journal’s head when it was exported, the decisions listed, the export’s filters: the verifier says how many later decisions are not in it.

What the check proves

What it does not prove

« anchor.tsr », « tsa-chain.pem » and « signature.jws » are outside the manifest: they bear on its root hash, which covers every other file.