Skip to content

Integrate SignPath production signing and SmartScreen validation - #150

Draft
dantraynor wants to merge 5 commits into
mainfrom
fix/windows-production-signing
Draft

dantraynor wants to merge 5 commits into
mainfrom
fix/windows-production-signing

Conversation

@dantraynor

@dantraynor dantraynor commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Signed Windows candidate builds currently stop at a provider placeholder. This change submits both Windows helpers to SignPath's fixed tailchrome / release-signing policy, builds the MSI from the signed x64 helper, and signs the outer MSI. The existing verifier checks the production publisher, trust, timestamps, and raw/embedded payload equality before candidate assembly. Signing request IDs and verification evidence are retained for 90 days.

Configuration checks reject missing credentials, conflicting signing modes, and production requests from an untagged or different repository. The release checklist now requires a browser-downloaded MSI with its Internet-zone marker intact, an Explorer launch, and recorded SmartScreen/policy observations. Related to #133; signing does not guarantee reputation or resolve an antivirus report by itself.

The October 20 SignPath dashboard inspection and the maintainer's October 21 screenshots (03:12 UTC) show Release certificate 2026 still CSR Pending, leaving release-signing invalid. Trusted-build verification, origin verification, and explicit maintainer approval are enabled; production activation awaits certificate issuance and verification. The personal signing-request queue shows no request awaiting maintainer approval; it is separate from certificate issuance.

The October 20 manual browser-download test of the public v0.1.15 MSI matched SHA-256 bb0b6053fd26b6433c2d0cbc1f970c4ebee5bbde26c23d76636d0f8ab533e1dd, retained ZoneId=3 before launch, and reported the expected NotSigned status. The maintainer reported no SmartScreen warning when opening it from Explorer on the retained Windows 365 Cloud PC. Windows Installer recorded a successful installation, and the installed helper matched the released x64 EXE.

Screenshots captured afterward show Check apps and files and SmartScreen for Edge enabled. Potentially unwanted app blocking is enabled with Block apps checked and Block downloads unchecked. The 08:52 UTC follow-up records Windows 11 Enterprise build 26300, running Edge 155.0.4283.62, Defender Normal with its queried protection flags enabled, Malwarebytes' service running, and Smart App Control in evaluation mode.

The follow-up MSI checksum still matches, but Zone.Identifier is now missing despite the recorded pre-launch ZoneId=3. Its removal time and cause are unknown; the checksum does not cover that alternate data stream. This remains a supplemental no-prompt observation on a reused machine, with continuous marker retention, effective policy/protection state at launch, Explorer token, and launch screenshots unestablished. It does not establish a standard-user or clean first-execution result, resolve #133, or validate a future signed candidate. Repository signing settings and published v0.1.15 assets have not changed.

Validation: 13 configuration checks pass under PowerShell 7.6.7; both workflows pass actionlint; all 27 embedded PowerShell blocks and both new scripts parse successfully. All PR checks pass, including Windows signature/packaging fixtures and native ARM64 smoke tests (CI run 39388691653).

Keep main's concise documentation and routing diagrams while preserving production signing and SmartScreen guidance.
@dantraynor
dantraynor marked this pull request as ready for review November 1, 2026 04:48
Upgrade vulnerable test and glob dependencies, replace the Firefox linter merge dependency, and preserve compatibility with existing consumers. Add dependency regression checks and enforce a clean audit at every severity in CI.
@dantraynor
dantraynor marked this pull request as draft November 5, 2026 10:03

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows Defender blocks helper

1 participant