Authenticode signing for alkane-toolkit.exe through Azure Artifact Signing (formerly Trusted Signing), set up end to end except for the one step Microsoft reserves for a person: the publisher identity validation.
Azure (already created)
Signing account blueflaresigning (Basic), resource group rg-blueflare-signing, West US 2.
CI identity alkane-toolkit-ci-signer, which can only sign (role: Artifact Signing Certificate Profile Signer). Its credentials are stored as Gitea secrets AZURE_SIGNING_*.
CI
ci/sign-windows.sh signs from Linux with jsign and adds an RFC 3161 timestamp. It runs in release.yml and next.yml before packaging.
Signing is a no-op until the repository variable AZURE_SIGNING_PROFILE is set. After that, any signing failure fails the build.
windows-native.yml verifies the signature with Get-AuthenticodeSignature on real Windows 11.
The CI image adds Java and a checksum-pinned jsign 7.6.
After identity validation
scripts/enable-windows-signing.sh <identity-validation-id> creates the certificate profile, narrows the signer to it, and turns signing on.
Tested: the signing path authenticates against the service (403 for a nonexistent profile with a real token, 401 with a bad one), and the skip path leaves builds unsigned.
Authenticode signing for alkane-toolkit.exe through Azure Artifact Signing (formerly Trusted Signing), set up end to end except for the one step Microsoft reserves for a person: the publisher identity validation.
## Azure (already created)
- Signing account `blueflaresigning` (Basic), resource group `rg-blueflare-signing`, West US 2.
- CI identity `alkane-toolkit-ci-signer`, which can only sign (role: Artifact Signing Certificate Profile Signer). Its credentials are stored as Gitea secrets `AZURE_SIGNING_*`.
## CI
- `ci/sign-windows.sh` signs from Linux with jsign and adds an RFC 3161 timestamp. It runs in `release.yml` and `next.yml` before packaging.
- Signing is a no-op until the repository variable `AZURE_SIGNING_PROFILE` is set. After that, any signing failure fails the build.
- `windows-native.yml` verifies the signature with `Get-AuthenticodeSignature` on real Windows 11.
- The CI image adds Java and a checksum-pinned jsign 7.6.
## After identity validation
`scripts/enable-windows-signing.sh <identity-validation-id>` creates the certificate profile, narrows the signer to it, and turns signing on.
Tested: the signing path authenticates against the service (403 for a nonexistent profile with a real token, 401 with a bad one), and the skip path leaves builds unsigned.
Generated with [Claude Code](https://claude.com/claude-code)
- ci/sign-windows.sh signs alkane-toolkit.exe from Linux with jsign through
the blueflaresigning account (RFC 3161 timestamped), using the
least-privilege CI service principal alkane-toolkit-ci-signer. It is a
no-op until the repository variable AZURE_SIGNING_PROFILE names a
certificate profile; after that any signing failure fails the build.
- release.yml and next.yml sign before packaging; windows-native.yml checks
the signature with Get-AuthenticodeSignature on real Windows and requires
Valid once signing is on.
- CI image adds a Java runtime and a checksum-pinned jsign 7.6 (re-pinned);
windows-ci.sh fetches the same jar on older images.
- scripts/enable-windows-signing.sh turns signing on after Microsoft
approves the publisher identity validation: creates the PublicTrust
certificate profile, narrows the signer role to it, sets the variable.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
noah
merged commit c06cff966d into main2026-11-02 19:51:17 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Authenticode signing for alkane-toolkit.exe through Azure Artifact Signing (formerly Trusted Signing), set up end to end except for the one step Microsoft reserves for a person: the publisher identity validation.
Azure (already created)
blueflaresigning(Basic), resource grouprg-blueflare-signing, West US 2.alkane-toolkit-ci-signer, which can only sign (role: Artifact Signing Certificate Profile Signer). Its credentials are stored as Gitea secretsAZURE_SIGNING_*.CI
ci/sign-windows.shsigns from Linux with jsign and adds an RFC 3161 timestamp. It runs inrelease.ymlandnext.ymlbefore packaging.AZURE_SIGNING_PROFILEis set. After that, any signing failure fails the build.windows-native.ymlverifies the signature withGet-AuthenticodeSignatureon real Windows 11.After identity validation
scripts/enable-windows-signing.sh <identity-validation-id>creates the certificate profile, narrows the signer to it, and turns signing on.Tested: the signing path authenticates against the service (403 for a nonexistent profile with a real token, 401 with a bad one), and the skip path leaves builds unsigned.
Generated with Claude Code