Skip to content

Document that releases ship unsigned while signing is on hold #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hsbt merged 1 commit into from
Oct 27, 2026
Merged

Document that releases ship unsigned while signing is on hold #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 12 additions & 13 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,8 +142,8 @@ directory on the user PATH, producing exactly the layout `rb setup`
creates, and removes both again on uninstall. rbmanager is a single MSI
product line; see [docs/upgrade-code.md](docs/upgrade-code.md). WiX
5.0.2 comes in through the `WixToolset.Sdk` NuGet package, and ICE
validation runs as part of the build. The MSI is currently unsigned;
only the release rb.exe is signed (see below).
validation runs as part of the build. The MSI is unsigned, and so is
the release rb.exe for now (see below).

An earlier iteration packaged each Ruby version as its own MSI. That
direction was dropped in favor of rbmanager; see the git history for
Expand All @@ -152,17 +152,16 @@ the sources and the verification record.
## Releases and code signing

Pushing a `v*` tag runs `.github/workflows/release.yml`, which builds
NativeAOT rb.exe for win-x64 and win-arm64, signs both, and attaches
them with `.sha256` checksums to a GitHub release. rb.exe is the one
binary users download directly with a browser, so it faces SmartScreen
with the Mark of the Web attached; it is the first signing target,
ahead of the MSI and winget channels. CI builds stay unsigned.

Free code signing provided by [SignPath.io](https://signpath.io),
certificate by [SignPath Foundation](https://signpath.org). The
signing step is isolated in `.github/actions/sign` so the provider can
be replaced later; the signing policy, the repository configuration,
and the SignPath application checklist are in
NativeAOT rb.exe for win-x64 and win-arm64 and attaches them with
`.sha256` checksums to a GitHub release. rb.exe is the one binary
users download directly with a browser, so it faces SmartScreen with
the Mark of the Web attached; it is the first signing target, ahead of
the MSI and winget channels. CI builds stay unsigned.

Code signing is on hold, so the release binaries are unsigned for now.
The signing step stays in place, isolated in `.github/actions/sign` so
the provider can be replaced later. The signing policy, the repository
configuration, and the SignPath application checklist are in
[docs/code-signing.md](docs/code-signing.md).

## CA trust bootstrap
Expand Down
3 changes: 3 additions & 0 deletions docs/code-signing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@
This document is the code signing policy for rbmanager and the
operating manual for the release signing pipeline.

Signing is on hold for now, so releases ship unsigned through the
draft path described below.

## What is signed, and why rb.exe first

The only signed artifacts are the release builds of `rb.exe`
Expand Down
Loading