You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sergio velderrain edited this page Nov 9, 2026
·
1 revision
REQ-063: Verify the actual NSIS executable hash before launch
Requirement
The Windows bootstrap launcher shall execute only an NSIS payload whose SHA-256 matches the expected executable hash for the current attempt.
Rationale
A correct volume label or filename does not establish which binary will run.
Fit Criterion
The host records the expected executable hash and the guest launcher independently hashes the exact file it will start; a mismatch, unreadable file, or inability to protect that file from replacement prevents execution. The source commit and binary hash are recorded separately and are not, by themselves, a reproducible-build attestation.
Verification
Planned, TEST-063; REQ-013's existing scope still excludes auxiliary-media hash verification.