Repository navigation
Prepare code signing with SignPath Foundation (off until set up) - #6
Merged
Merged
Conversation
The release workflow can now sign CryptBridge.exe with SignPath, but only once the repository has the variable SIGNPATH_ORGANIZATION_ID and the secret SIGNPATH_API_TOKEN. Without them it builds unsigned exactly as before. The rclone and WinFsp copies are never sent for signing. - Every release build checks name and version in the exe's file properties, because SignPath only signs matching files. - Dry run: by hand on any branch (tick "dry run") and for pull requests that change the release workflow, the build scripts or .signpath/. Nothing is tagged or published, the exe stays on the run page. - CODE_SIGNING.md: code signing policy with roles, privacy policy, the system changes (autostart, firewall rule) and uninstalling; linked from the README and from every release text. - README: SmartScreen note and an Uninstalling section. - .signpath/: artifact configuration, file check, setup and removal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GvUq7HnA5ggbuHBogzS2rV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GvUq7HnA5ggbuHBogzS2rV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares free code signing through the SignPath Foundation. Nothing changes for releases until it is switched on: without the variable
SIGNPATH_ORGANIZATION_IDand the secretSIGNPATH_API_TOKENthe release workflow builds unsigned, exactly as before.What changes
CryptBridge.exeonly. The rclone and WinFsp copies are never sent for signing (SignPath forbids signing other projects' binaries). Every release build checks name and version in the exe's file properties. The release text ends with a line linking the code signing policy.build.ps1,release-assets.ps1or.signpath/. Nothing gets tagged or published; dry runs use their own concurrency group.docs/technical.mdmentions the dry run and signing.Before merging
CODE_SIGNING.mdsays all team members use 2FA on GitHub and SignPath. Please make sure that is true.Generated by Claude Code