Repository navigation
Code Signing
Documentation snapshot from docs/CODE_SIGNING.md at commit
20d7c81. Check the current source for updates.
KubeFactory · All docs · 2.0.0-beta.2 pre-release · Known limitations
| Platform | Signed by | Status |
|---|---|---|
Windows (KubeFactory.exe, KubeFactory.console.exe, kf-agent.exe) |
SignPath Foundation, through SignPath | Wired up, not active yet. The release workflow signs once the project is approved by SignPath Foundation and the settings below exist. Until then the Windows package is unsigned and SmartScreen warns on first run |
| macOS | ad-hoc only | Not notarized: there is no Apple developer identity |
| Every package | GitHub artifact attestation (Sigstore) | Active: gh attestation verify <package> -R DasCondor/kubefactory
|
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
This applies once SignPath Foundation has approved the project.
-
What is signed: the Windows executables built by
.github/workflows/release.ymlfrom a tagged commit of this repository:KubeFactory.exe,KubeFactory.console.exeandkf-agent.exe. Nothing built anywhere else, and no third-party binary, is signed. - Roles: committer, reviewer and approver: DasCondor. Every release signing request is approved by hand on SignPath.
- Privacy: KubeFactory does not send information to other networked systems unless you ask it to: it talks to the clusters, Docker engines, Komodo Core, KubeFactory server, Grafana, Tautulli or AI provider you configure, and to the app lists you choose. There is no telemetry. See SECURITY.md.
- Apply at signpath.org for the free open-source certificate. The project qualifies on its face (MIT, public repository, releases built by GitHub Actions); SignPath Foundation decides. Everyone with access must use multi-factor authentication on GitHub and SignPath.
- On SignPath: add the predefined GitHub.com trusted build system and
link it to the project; create the project (slug
kubefactory) and a signing policy (slugrelease-signing) that needs manual approval; paste.signpath/artifact-configuration.xmlas the project's artifact configuration; install the SignPath GitHub App on the repository. - On GitHub (Settings > Secrets and variables > Actions):
- variable
SIGNPATH_ORGANIZATION_ID: the organisation id from SignPath - secret
SIGNPATH_API_TOKEN: an API token of a SignPath user who may submit to that project and policy - optional variables
SIGNPATH_PROJECT_SLUGandSIGNPATH_POLICY_SLUGif the slugs differ from the ones above
- variable
- Tag a release. The Windows job uploads the package, waits (up to an hour)
for the signing request to be approved, puts the signed package in its
place, checks that every
.exein it carries a valid Authenticode signature (the job fails otherwise), writes its checksum and attests it.
Only free signing is used. SignPath Foundation's certificate costs nothing for open-source projects; the trade-off is that Windows shows SignPath Foundation as the publisher, not the project's author. Paid certificates are deliberately not wired up.
Not tested: none of this has run yet. The workflow skips the signing steps until the variable exists, so releases keep working unsigned. The artifact configuration should be checked in SignPath's editor the first time.
Start
Visual guides
Operations
- Storage and screens
- LiveView
- Krew and Foreman
- Porter and Bob
- Text editor
- Logs
- Teams
- Administration
- Server mode
- Docker hosts
- Security
- Known limitations
Development and reference