Skip to content

Dodaios is an open-source agent OS for your desktop: it runs your coding agents, browser and apps by voice or chat, on your own machine. Formerly Personal Jarvis.

5.2 KB
Raw Blame

Code signing policy

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

Status: Dodaios (formerly Personal Jarvis) has applied to the SignPath Foundation open-source program. Until the application is approved and the first signed release ships, the Windows installer on the Releases page is unsigned. Each release's workflow log states whether it was signed.

What is signed

Artifact Platform Signed by
Dodaios-Setup-x64.exe Windows 10/11 x64 SignPath Foundation certificate, via SignPath.io

The setup's product name is Dodaios. After signing, the release publishes the same signed file a second time as PersonalJarvis-Setup-x64.exe, the name installs from before the rename look for; the two downloads are byte-identical, so both carry this signature. That copy has a planned end (PUBLISH_EARLIER_INSTALLER_NAMES in scripts/ci/release_assets.py).

Only files built from this repository's source code by the Desktop installers GitHub Actions workflow are submitted for signing. The workflow runs on GitHub-hosted runners for a release tag. SignPath.io verifies that each submitted file was produced by that workflow before it signs anything. Third-party components bundled in the installer keep their own publishers' signatures (or none). They are never signed with this project's certificate.

The macOS disk images and the Linux AppImage are not covered by this policy.

Team roles

Role Who
Committers and reviewers Members of the Dodaios organization
Approvers Owners of the Dodaios organization
  • Committers may change the source code in this repository.
  • Reviewers review every pull request from people outside the team before it is merged.
  • Approvers approve each signing request in SignPath by hand. No release is signed without that approval.

All team members use multi-factor authentication for GitHub and SignPath.

How a release gets signed

  1. A maintainer pushes a v*.*.* release tag.
  2. The workflow builds the installer and uploads the unsigned file as a workflow artifact.
  3. The workflow sends a signing request to SignPath.io, which checks the file's origin.
  4. An approver reviews the request and approves it in SignPath.
  5. The workflow downloads the signed installer, checks that its Authenticode signature is valid, timestamped and issued to SignPath Foundation, and only then publishes it.

Privacy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it. Dodaios contacts a service only when you connect and use it, for example a model provider, a speech provider or a plugin you configured. Those services handle data under their own privacy policies. Details are in Privacy and Local Data and the privacy section of SECURITY.md.

Report a problem

If you believe a file signed with this project's certificate is malicious or breaks this policy, report it privately as described in SECURITY.md. You can also contact SignPath at [email protected].

Maintainer setup

The signing path in the workflow stays dormant until these are set in the repository settings:

Kind Name Value
Secret SIGNPATH_API_TOKEN API token of a SignPath user with submitter rights
Variable SIGNPATH_ORGANIZATION_ID SignPath organization ID
Variable SIGNPATH_PROJECT_SLUG SignPath project slug
Variable SIGNPATH_SIGNING_POLICY_SLUG Signing policy slug, usually release-signing
Variable (optional) SIGNPATH_ARTIFACT_CONFIGURATION_SLUG Artifact configuration slug; empty uses the project default

The workflow uploads the installer as a ZIP workflow artifact, so the SignPath artifact configuration wraps the setup file in a ZIP and pins its metadata:

<artifact-configuration xmlns="http://signpath.io/artifact-configuration/v1">
  <zip-file>
    <pe-file path="Dodaios-Setup-x64.exe" product-name="Dodaios">
      <authenticode-sign />
    </pe-file>
  </zip-file>
</artifact-configuration>

The file name and the product name are pinned in three places that must always agree: this configuration, SignedSetupBaseName and SignedProductName in packaging/windows/Dodaios.iss, and SIGNED_SETUP_NAME in the windows job of .github/workflows/desktop-installers.yml (tests/unit/ci/test_installer_aliases.py checks the repository side). Releases up to 4.1.2 built the setup as PersonalJarvis-Setup-x64.exe with the product name Personal Jarvis; no release was signed under that name, so a configuration entered in SignPath before this change must be updated to the values above before the first signed release.

Without these settings the workflow prints a notice and publishes an unsigned installer. If both SignPath and Azure Trusted Signing are configured, SignPath is used.