From 08e22806470e0cf1b0513d831e6abf2e89801b24 Mon Sep 17 00:00:00 2001 From: ofhd Date: Tue, 22 Sep 2026 10:19:59 -0700 Subject: [PATCH] Stamp the verified rc.4 Windows digest into the run page The frozen GUI executable was rebuilt from 5d379c7 on the owned Windows host, hash-verified there (2ec0a4bc...c0379, 180,189,569 bytes), accepted through the native recovery/consent sweep, and merged as PR #19. The page rendered "SHA-256 published with the release" for the primary Windows download until this one line exists; with it, the page names the exact bytes users must match before running. The console companion digest ships in the release SHA256SUMS, not on the page, matching rc.3. No other field changes: rc.3 digests stay as published history, and the Mac/Linux entries already carry their verified byte-identical digests. --- frontend/app/run/releaseAssets.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/app/run/releaseAssets.ts b/frontend/app/run/releaseAssets.ts index 16e40fa0..1e796468 100644 --- a/frontend/app/run/releaseAssets.ts +++ b/frontend/app/run/releaseAssets.ts @@ -53,7 +53,7 @@ export const primaryAssets: ReleaseAsset[] = [ { file: "encodingdb-client-windows.exe", label: "Windows (GUI)", - sha256: null, + sha256: "2ec0a4bcb7d94af340e61a1837bfc9380b51b2dd60bbd1f48eb023dfa24c0379", support: "No Authenticode signature, so SmartScreen may warn at first launch. The window exposes the same Small/Medium/Large/Full sweeps as the guided interface and recovers automatically from a cache folder protected against the current user.", }, {