Install ElastOS from a signed release packed inside a desktop installer

未關閉
  • 哪裡不對？
#520 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
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 小時
30 天內合併 PR
42

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

elastos/elastos-runtime 的其他 Issue

查看 elastos/elastos-runtime 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。