CodeNomad/CODE_SIGNING.md
Pascal André 2f153e2e34
Some checks are pending
Download Caches / seed (macos-15-intel) (push) Waiting to run
Download Caches / seed (macos-26) (push) Waiting to run
Download Caches / seed (ubuntu-24.04) (push) Waiting to run
Download Caches / seed (windows-2025) (push) Waiting to run
Publish help / build (push) Waiting to run
Publish help / deploy (push) Blocked by required conditions
fix(security): qualify electron-builder 26 before Windows signing (#1459)
fix(security): qualify electron-builder 26 before Windows signing

Resolve the ten remaining builder/runtime/tar alerts with electron-builder and app-builder-lib 26.18.0, builder-util-runtime 9.7.0 and tar 7.5.22. Declare the server tests' actual AJV 6 dependency so builder's AJV 8 hoisting cannot change their API; preserve the separate AJV2020 alias and production AJV 8.

Before the Windows builder CLI starts, apply the three-line reviewed resource-editor correction behind an exact source hash and version fence. Keep full stable/prerelease ProductVersion and FileVersion strings alongside their numeric Windows prefixes. The actual packager edits resources before signIf; unsigned and signed metadata checks remain unchanged.

Integrate the qualified PWA/runtime dependency graph rather than overwrite its lockfile. Correct the new minimatch consumers through family-scoped overrides, retain historical ASAR/temp callback APIs and remove config-file-ts's unused closure. Qualify actual matching, file copies, ASAR merges, TypeScript configuration, cancellation and resource-edit ordering.

Frozen Windows/Linux installs, consumer tests, typechecks, complete builds, real offline PWA behavior and the normal Windows packaging/executable smoke qualify the combined candidate. The existing blocked Dependabot proposal stays visible until this tested replacement is merged and its alerts are independently checked.


Include the explicitly user-authorized artifact announcer permission pair (PR-write, Issues-read), guarded by thirteen helper tests and the unchanged trusted-default-branch boundary. No new secret or protection change.

Capture original Windows identity probes in the test fixture instead of a second misleading diagnostic lookup. Preserve the shared identity budget, retries and fencing; fifteen Node and eighteen native module checks pass. The initial OS incident remains open in #1462. Incorporate the already merged GLib backport and verify the complete 4,456-file tree before final full CI.
2026-11-11 03:56:42 +01:00

5.4 KiB

Code signing policy

Status: CodeNomad is a SignPath Foundation project. The release workflow signs Windows files with SignPath's test certificate on request; stable Windows releases stay unsigned until SignPath Foundation issues the release certificate.

Responsibilities

Role Maintainer Responsibilities
Project owners Shantur Rathore (@shantur) and Pascal André (@pascalandr) Own project governance, authorize the signing integration and approve changes to signing responsibilities.
Signing operator and approver Pascal André (@pascalandr) Coordinates the application, maintains the signing workflow, submits and approves release signing requests, and verifies signed artifacts before publication.
Authors and reviewers Shantur Rathore and Pascal André Maintain the source and build workflows, and review contributions before they enter the release build.

Everyone involved in signing must use multi-factor authentication for GitHub and SignPath access.

Signing provider

The provider is SignPath.io, with a certificate provided by SignPath Foundation through its open-source program. Certificates under this program identify SignPath Foundation as the publisher.

The attribution for releases signed through the program will be:

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

What is signed

Only files built from this repository are signed; bundled third-party files keep their own signatures (the OpenJS Foundation's node.exe) or stay unsigned (Electron's Chromium libraries).

Release asset Signed files
CodeNomad-Tauri-windows-x64-<version>.exe (installer, WinGet package and in-app update) The installer and the codenomad-tauri.exe application it installs
CodeNomad-Electron-windows-x64-<version>.zip (portable) CodeNomad.exe inside the archive

The uninstaller the Tauri installer writes is generated while the installer is built and is not signed.

Release signing

  1. Windows CodeNomad executables and installers are built from the public CodeNomad repository on GitHub-hosted Actions runners, from an identified release commit (.github/workflows/build-and-upload.yml).
  2. Each job uploads the unsigned files as a GitHub Actions artifact and submits it to the SignPath project CodeNomad (.github/actions/signpath-sign), which verifies the artifact's origin before signing. Three signing requests are made per release: the Tauri application, then the Tauri installer that packages the signed application, and the Electron archive.
  3. The artifact configurations in .signpath/artifact-configurations/ (kept identical to those in SignPath) list the exact files and require the product name CodeNomad and the release version as the product version of every signed file. Tauri writes the full release version; for Electron, packages/electron-app/scripts/build.js passes it to electron-builder as shortVersionWindows. Before invoking Windows packaging, it applies the reviewed, hash-checked patch-builder-resources.cjs correction to the pinned builder's resource editor. The editor writes the full ProductVersion and FileVersion strings and their numeric Windows prefixes into CodeNomad.exe before its signing call. An unexpected editor or builder version fails the build.
  4. Pascal André reviews and manually approves each release signing request in SignPath. The workflow waits up to two hours for each approval.
  5. Before submission the workflow checks each file's product name and version (Electron's on every build); afterwards it verifies the returned Authenticode signature, its timestamp, the SignPath Foundation signer and the product version, and that the contents of the Electron archive differ from the build only in CodeNomad.exe.
  6. The Tauri updater signature is recomputed over the signed installer, and the update manifest, release asset digests and WinGet hash are taken from the published signed files. Release records identify the source commit and build workflow.

Signing access and policy changes are reviewed by the project owners. The operator investigates failed verifications and reported signing-policy issues.

Workflow configuration

Setting Effect
Secret SIGNPATH_API_TOKEN API token of the SignPath CI submitter. Pull requests and forks never receive it and build unsigned.
Variable SIGNPATH_RELEASE_SIGNING = true Stable releases use the release-signing policy. A release then fails, rather than publishing unsigned Windows files, when the token is missing or signing or verification fails.
SignPath Test Signing workflow Builds a branch and signs its Windows files with the test-signing policy without publishing; the signed files are kept as run artifacts.
Develop Pre-Release input signpath_test_signing Publishes a dev prerelease whose Windows files carry the test signature.

Test signatures chain to a certificate Windows does not trust; verification accepts that only for the test-signing policy.

Privacy

CodeNomad's network connections and data handling are described in the Privacy policy.