* Map downloads are checked against the hash in the signed manifest
A meta4 signs only a bare hash, so any genuinely signed meta4 (an older version of a region, another region) passed
its own check. The manifest now lists each file's sha256; it is signed as a whole, so the hash is tied to the URL.
The catalog copies each hash into its download's settings, and aria2c checks the file against it. Downloads from a
manifest without hashes still require the file's signed meta4.
build_map_regions.py writes the hashes, and hash_map_manifest.py adds them to the published manifest from the
verified meta4s without rebuilding any maps.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* hash_map_manifest.py hashes each file's bytes instead of trusting its meta4's name
Only the bare hash in a meta4 is signed, so an older version's meta4 with its name rewritten (or terrain's, whose name
never changes) passed the name and duplicate-hash checks. Each file is now hashed from a local copy of the published
files (--files) or downloaded from the CDN, and must match its signed meta4.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>