Matthias JakischDeutsch

Verify

A rule only counts if it was fixed before its results were known. Here is how that is recorded and how you can check it yourself.

How a seal works

  1. Rule, configuration, plan and decision date are written down before the forward start, without any result on the data the decision will use.
  2. For each of these files the SHA-256 is computed: a fingerprint that changes completely if a single character changes. The seal file (.sha256) lists them; I confirm it, and it is committed to my repository.
  3. The code that books the shadow books is bound by its own hash, recorded in the registration contract.
  4. Two independent public timestamp authorities sign the SHA-256 of each seal file (RFC 3161). Their signed replies are here for download.
  5. On the decision date the forward results are measured against the criteria of the registration. Changes are possible only as a new, dated registration or amendment, listed in the register.

Check it yourself

With OpenSSL (on Windows it comes with Git for Windows). Example: the seal of AT-UT and its configuration.

# 1. Fingerprint of the configuration; compare with its line in the seal file
sha256sum schatten-atu-v1.json
# 2. Fingerprint of the seal file; compare with the register
sha256sum registrierung-atu.sha256
# 3. Show the timestamp: time and the hash it signs
openssl ts -reply -in docs--validation--registrierung-atu.sha256.digicert.tsr -text
# 4. Check signature and hash against the seal file
openssl ts -verify -data registrierung-atu.sha256 -in docs--validation--registrierung-atu.sha256.digicert.tsr -CAfile digicert-trusted-root-g4.crt
openssl ts -verify -data registrierung-atu.sha256 -in docs--validation--registrierung-atu.sha256.freetsa.tsr -CAfile freetsa-root.crt

Both checks end with “Verification: OK”. The root certificates are the published roots of the two authorities.

What the evidence shows, and what not

Code hash AT-UT

SHA-256 over 232 source files of the booking code, recorded in the registration contract: dcceddcbd55b0ddb86e58a0d9c453473b48bb11e25455dd612c85df204f301af

Downloads

Seal files

Registration contracts and configurations

Amendments

Root certificates of the timestamp authorities

The timestamp replies are linked next to each file in the register.

Repository state of this page: 34eae03debd23a241556cf246ccbbf1374b55d54.