Skip to content

Apply to SignPath Foundation for free OSS code signing #208

Open

Description

@DeepDiver1975

Goal

Get the Windows MSI (and ideally other artifacts) code-signed via SignPath Foundation's free program for open-source projects, so releases stop showing "Unknown Publisher" / SmartScreen warnings.

Why SignPath

  • Free OV-level code signing for qualifying OSS projects, GitHub Actions native.
  • Alternatives ruled out: Microsoft Trusted Signing individual-developer onboarding is currently paused (2026); Certum/SSL.com discounted certs are paid fallbacks.

Eligibility checklist (signpath.org/terms)

  • OSI-approved license without dual-licensing (MIT)
  • No proprietary/non-OSS components
  • Actively maintained
  • Already released in signable form (MSI via GitHub Releases)
  • Functionality documented (README)
  • Published code-signing policy on project homepage (needed before signing starts, not for application)
  • Defined Author/Reviewer/Approver roles (can be solo maintainer as Approver)
  • MFA enabled on GitHub for all team members (to verify)

Status

Application in progress — this issue will be updated with the outcome once submitted.

Activity

  1. DeepDiver1975 commented on Sep 4, 2026

    @DeepDiver1975
    ContributorAuthor

    Status: could not auto-submit — drafted answers below

    The application at signpath.org/apply is a JS-rendered HubSpot form with no reachable public API from here (its embed/submission endpoints 404'd against this environment), and browser automation (claude-in-chrome) isn't set up in this session. Rather than blind-POST to a guessed HubSpot endpoint and risk a silently broken or spam-flagged submission on a real application, I stopped and drafted the content for manual submission — takes ~2 minutes at https://signpath.org/apply.

    Drafted answers

    • Full name: Thomas Müller
    • Email: (fill in privately when submitting — not posted here)
    • Company/Organization: CodeForFire
    • Project name: Lagebuch
    • Repository URL: https://github.com/CodeForFire/lagebuch
    • License: MIT — https://github.com/CodeForFire/lagebuch/blob/main/LICENSE
    • Download/Release URL: https://github.com/CodeForFire/lagebuch/releases
    • Project description:

      Lagebuch ("log book") is an offline-first incident documentation (Einsatzdokumentation) desktop application for fire brigade command vehicles (ELW). Volunteer and professional fire brigades use it to log incidents, track units and personnel, monitor SCBA (Atemschutz) teams, manage tasks, and generate PDF reports — fully offline, with optional multi-device sync. Built with .NET 8 + Avalonia. Distributed via GitHub Releases as: Windows MSI, Linux .deb, Android APK, and macOS .dmg.

    Still open after submission (per eligibility checklist above)

    • Publish a visible code-signing policy on the project homepage/README once SignPath responds — not needed for the application itself.
    • Confirm GitHub MFA is enabled for the account/org.
    • Define Author/Reviewer/Approver roles (solo maintainer can be sole Approver).

    Next step: submit the form manually with the answers above, or re-run this with /chrome enabled so I can drive the actual submission.

  2. self-assigned this
    on Sep 4, 2026
  3. DeepDiver1975 commented on Sep 11, 2026

    @DeepDiver1975
    ContributorAuthor

    SignPath: rejected — and the OSS alternatives, assessed

    SignPath Foundation did not accept the application. Nothing in their terms was
    violated (MIT, public source, actively maintained, released in signable form);
    the gap is demonstrable adoption — this repo was created 2026-06-21 and has no
    public download history yet. That is a matter of time, not a fixable defect in
    the application.

    The 2026 landscape for a solo, unincorporated maintainer

    Option Verdict
    Microsoft Store (MSIX) ✅ Free, and the Store re-signs the package with a Microsoft certificate — no SmartScreen at all. Individual registration is free worldwide since late 2025. Tracked separately, see below.
    Azure Artifact Signing (ex-Trusted Signing) ❌ ~$9.99/mo, and eligibility is organizations in US/CA/EU/UK; individuals only US/CA. Blocked on both counts.
    Certum Open Source Code Signing ❌ ~$50/yr, and SimplySign has no headless CI story — automation needs a VNC/p11-kit container on a self-hosted runner.
    OV certificate (DigiCert/Sectigo/GlobalSign) ❌ $150–300/yr.
    EV certificate ❌ $400+/yr and pointless: EV stopped bypassing SmartScreen in 2024 and now builds reputation exactly like OV.
    OSSign (ossign.org) ⏳ Free, credible — but closed to us right now, see below.
    Self-signed ❌ Worse than unsigned: a hard SmartScreen block for anyone who has not installed the root.
    Sigstore / GitHub build attestations ⚠️ Free and real, but does not affect SmartScreen. Worth doing for provenance, not as the fix.

    OSSign (ossign.org) — the closest free equivalent, currently unavailable

    A Swedish outfit (maintainer @scheibling, backed by
    Scheibling Consulting AB, Cloudyne Systems and Clysec) that signs OSS binaries with
    their own EV certificate via a GitHub Actions dispatch/approval flow. Real track
    record — LibrePCB, LibreWolf, WebCord, DiskCryptor, Beaver Notes and ~45 other
    projects are signed through it.

    Two blockers, both temporal:

    1. Applications are suspended. From their site: "Applications are currently
      suspended due to a high workload and large backlog while we focus on assessing
      and responding to the applications in the queue."
      Their contact form adds:
      "We are not accepting applications for code signing through this contact form."
    2. We fail their activity bar anyway. "There is an absolute minimum of 6 months
      of activity on your account, organization and project."
    Created 6-month mark
    DeepDiver1975 2011-08-25 ✅
    CodeForFire org 2026-08-21 ❌ 2027-02-21
    CodeForFire/lagebuch 2026-06-21 ❌ 2026-12-21

    The binding date is the organisation: earliest application ~21 February 2027,
    and only if applications have reopened by then.

    Criteria we would otherwise meet: MIT with all release code public; a CI pipeline
    where the build is verifiable and each release binary is traceable to its source,
    including code-quality checks; not commercial; and clearly not "software or other
    tools that have a clear political or controversial purpose."

    Worth noting for later: OSSign signs with their certificate, so the maintainer's
    real name need not appear on the signature — "since we sign the binaries with our
    certificates your real name does not have to appear anywhere on the certificate,
    signature or binary if you do not want it to."

    Where that leaves this issue

    There is no free route that signs the GitHub Releases MSI on our own certificate
    today. The MSI stays unsigned for now.

    • Microsoft Store (MSIX) is the one option that removes the SmartScreen warning
      now, and is tracked in its own issue.
    • Re-apply to OSSign after 2027-02-21, and re-apply to SignPath once there
      is real brigade adoption and download history to point at.

    Nothing to action here in the meantime; keeping this issue open as the record of
    the decision.

  4. added
    enhancementNew feature or request
    packagingRelease, distribution and code-signing infrastructure
    on Sep 21, 2026
  5. DeepDiver1975 commented on Oct 16, 2026

    @DeepDiver1975
    ContributorAuthor

    Parked, no milestone. winget (#209) already gives a SmartScreen-free install for the common case, so signing is no longer a release blocker. It stays open because one case still needs it: Behörden IT running AppLocker/WDAC or deploying through Intune/SCCM. There, an unsigned MSI can only be allowed by a hash rule, and every release breaks that rule. A publisher rule needs a signature. Pick this up again when a Feuerwehr's IT asks for it.

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpackagingRelease, distribution and code-signing infrastructure

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions