The Windows binary is signed by SignPath Foundation
Windows greets an unsigned one-file PyInstaller build as a stranger every release: SmartScreen warns, and antivirus engines flag it on sight. A signature gives Windows a publisher to accumulate trust against instead. SignPath Foundation issue the certificate free to open-source projects and sign on their own infrastructure, so no key exists on the runner. Their condition is that the artifact provably came from this repository's CI, which is why the binary is handed over as a GitHub artifact id rather than uploaded -- SignPath reads the workflow run behind it. Signing sits between the build's smoke test and the naming step, so the checksum describes the file people actually download. The unsigned draft is the one artifact the release must not attach, so it is named outside the meshterm-* pattern the release now downloads by. Both steps skip wholesale until SIGNPATH_ORGANIZATION_ID is set, so the Windows binary keeps building unsigned in the meantime and a fork with no SignPath project of its own is unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
bde2a08b7b
commit
c7c1770d96
2 files changed
+48
No files matched your search
@@ -55,6 +55,10 @@ jobs:
|
||||
# Every platform's artifact, flattened into one directory of files to attach.
|
||||
- uses: actions/download-artifact@v4
|
||||
with:
|
||||
# The build uploads one artifact nobody should ever download: the unsigned
|
||||
# Windows binary it hands to SignPath. Everything meant for the release page is
|
||||
# named `meshterm-…`, so the pattern is the filter.
|
||||
pattern: meshterm-*
|
||||
path: artifacts
|
||||
merge-multiple: true
|
||||
|
||||
|
||||
Reference in new issue
Block a user