EVIDE EAR Offline Verifier
Prototype. Checks the SHA-256 fingerprints of the files of an EVIDE evidentiary package. Runs entirely in this page: files are read by your browser and never sent anywhere.
What this tool does and does not do. This tool checks whether files match the fingerprints you supplied. It does not establish who produced the files unless a qualified signature is validated separately, it does not make the EVIDE receipt time qualified, and it cannot tell whether records are missing from the set you are examining. It does not replace a FEDIS.
1. Files
The checks run automatically as soon as the files are loaded. For a complete check, drop all four files together: the EAR, the canonical JSON and their two .sha256 checksum files. The page then moves to the results.
Drop files here or click to choose them.
Accepted: EAR text files (evide-ear-…-vN.txt), canonical JSON (evide-canonical-….json) and their .sha256 checksum files. Other files are listed but not used.
No files loaded yet.
2. Reference fingerprints copied from a FEDIS (optional)
A FEDIS cites the SHA-256 of the canonical JSON and of the EAR version it refers to. If you copy them here, they are treated as references supplied by you. This tool does not read the FEDIS and does not validate its signature or time stamp.
SHA-256 engine: checking…
3. Fingerprint checks
3b. Consistency between EAR versions
4. Checks performed
| Check | Compared | Outcome | Explanation |
|---|
5. Files read
| File | Detected as | SHA-256 of the file bytes | Notes |
|---|
6. Values stated inside the EAR
Outcomes used.
- MATCH the computed SHA-256 equals the reference it was compared with.
- MISMATCH the computed SHA-256 differs from that reference.
- NOT CHECKED the comparison was not made: material missing, reference ambiguous, format not recognised, or a technical error. It is never a finding of alteration.
- NOT VERIFIABLE WITH PROVIDED MATERIALS used in the downloadable report for authenticity, time and completeness: the property cannot be established from these files with this tool.
SHA-256 is computed on the exact bytes of each file. Nothing is re-encoded, normalised or re-canonicalised. A file re-saved by an editor (different line endings, an added byte order mark) has different bytes and therefore a different fingerprint.