Install ElastOS from a signed release packed inside a desktop installer

オープン
  • 何か問題がありますか？
#520 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
rust
領域
backend, security

調査の方向性

Read the install.sh flow and the existing install-release transaction, then inspect the unpublished lab/standalone-install branch referenced in the issue. Trace how release signatures, publisher DID, checksums, version and channel are validated before installation, and review the linked issues #518 and #519 for the startup and status boundary. Done means a local signed release installs through the existing transaction, preserves an existing Home, and passes the listed acceptance checks.

索引モデルが issue の本文から書いたものです。

説明

enhancement
Problem

A desktop installer (a Mac DMG or a Linux package) should install ElastOS without a terminal. 2.0.0 can only install through install.sh, which downloads from the seed and runs elastos install-release. There is no way to install from a copy of the signed release that ships inside an app.

The desktop app draft (Elacity/elastos-agent-host-spike#1386) calls elastos install --from DIR and a quiet start (ELASTOS_SERVICE=1). Both live only on a lab branch (lab/standalone-install) that is not pushed anywhere, so the draft cannot install the published 2.0.0 release.

Expected behaviour
  • Push lab/standalone-install to this repository as a pull request against develop, or replace it with one, implementing the points below. The desktop app is then rebuilt against the published release, not a lab Runtime.
  • One Runtime command installs from a local folder of signed release files with the same checks as install.sh: the release head's signature against the publisher DID baked into the app at build time, the release it names, every file's checksum, version and channel. Nothing from the folder runs before those checks pass. Lab publishers are refused in release builds.
  • It reuses the existing install transaction (install-release) rather than a second installer, so locks, downgrade and channel refusal, and interrupted-install recovery behave the same.
  • It records the normal trusted source and channel, so the installed Home updates from the seed like any other Home.
  • An existing Home for this user is adopted, never overwritten or doubled.
  • Optional large parts (the Browser image, about 900 MB) are fetched later on demand, not required in the folder.
  • Status (installed, starting, ready, failed with a reason) and starting Home without opening a browser come from #518; this issue adds only the install-from-folder result.
Acceptance
  • A folder with a valid 2.0.x release installs and Home becomes ready.
  • A folder with a bad signature, a changed file or a lab publisher is refused before anything from it runs, and nothing is written.
  • Interrupted install, run again: completes once.
  • Existing terminal-installed Home: adopted, data and passkeys kept.
  • After install, the Home finds the next release on the seed.
Links

Elacity/elastos-agent-host-spike#1386, #518, #519, #172, #452.

主要言語
Rust
スター
6
フォーク
2
平均マージ
1日 3時間
マージ済み PR（30日）
42

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

elastos/elastos-runtime のほかの issue

elastos/elastos-runtime の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。