Skip to content

Migrate code signing to the 2026 secrets - #541

Merged
georgestagg merged 1 commit into
mainfrom
fix-windows-signing
Sep 11, 2026
Merged

georgestagg merged 1 commit into
mainfrom
fix-windows-signing

Conversation

@georgestagg

Copy link
Copy Markdown
Collaborator

The signing credentials have been re-issued under new _2026 names, and SM_CLIENT_CERT_FINGERPRINT has been replaced by a keypair alias.

signtool /sha1 takes a thumbprint and has no alias form, so signing moves to smctl sign --keypair-alias, which no longer needs the certificates synced into the Windows store first. Verification now also checks the signature status, timestamp and signer name.

The signing credentials have been re-issued under new `_2026` names, and
`SM_CLIENT_CERT_FINGERPRINT` has been replaced by a keypair alias.

`signtool /sha1` takes a thumbprint and has no alias form, so signing
moves to `smctl sign --keypair-alias`, which no longer needs the
certificates synced into the Windows store first. Verification now also
checks the signature status, timestamp and signer name.

Mirrors posit-dev/assistant#1935.
@georgestagg
georgestagg merged commit 809da0a into main Sep 11, 2026
6 checks passed
@georgestagg
georgestagg deleted the fix-windows-signing branch September 11, 2026 08:44
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.

1 participant