Skip to content

Installer integrity: serve install.sh and release files only as the signed set #187

Closed as duplicate

Description

@andersalm

Part of #173 (isolation plan).

The gateway serves install.sh from the Publisher folder in the Runtime's data dir (elastos/crates/elastos-server/src/api/gateway_site.rs:150-180). install.sh carries the only trust anchor for new installs: the stamped maintainer DID. A process running as the Runtime account can rewrite it.

Done means

  • release.json carries the installer's SHA-256. The gateway serves install.sh, release-head.json, release.json and artifacts only when they match the signed publication set.
  • A test changes install.sh on disk and proves the gateway refuses to serve it.

The maintainer DID is published on GitHub by #186.

Activity

  1. added this to the 0.7.3 milestone on Oct 1, 2026
  2. andersalm commented on Oct 1, 2026

    @andersalm
    ContributorAuthor

    Merged into #186 so this concern has one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions