Skip to content

docs(signing): add code signing policy and Windows version resource for SignPath - #850

Merged
Karib0u merged 2 commits into
mainfrom
local/signpath-terms-review-fdf87f
Oct 19, 2026
Merged

Karib0u merged 2 commits into
mainfrom
local/signpath-terms-review-fdf87f

Conversation

@Karib0u

@Karib0u Karib0u commented Oct 19, 2026

Copy link
Copy Markdown
Owner

Summary

The SignPath Foundation terms require a public code signing policy and version metadata on signed binaries.

  • Add docs/code-signing-policy.md with the SignPath attribution, team roles and privacy statement.
  • Link it from the README, the docs nav and the release body.
  • Embed a PE version resource (ProductName = Rustinel, version from Cargo.toml) on Windows builds via winresource.
    It is skipped on non-Windows hosts.

Not verified

  • The resource compile only runs on a Windows host.
    Run the SignPath Dry Run workflow to confirm rustinel.exe carries the product name and version.
  • The SignPath project name must match Rustinel.
  • Roles list Karib0u only; confirm that is correct.

…or SignPath

SignPath Foundation terms require a public code signing policy on the home
and release pages, and ProductName/ProductVersion metadata on signed binaries.

- Add docs/code-signing-policy.md (attribution, roles, privacy) and link it
  from the README, the docs nav and the release body.
- Embed a PE version resource on Windows builds via winresource, skipped on
  non-Windows hosts.
@Karib0u
Karib0u enabled auto-merge (squash) October 19, 2026 20:06
@Karib0u
Karib0u merged commit 514e62a into main Oct 19, 2026
23 checks passed
@Karib0u
Karib0u deleted the local/signpath-terms-review-fdf87f branch October 19, 2026 20:12
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