Browser guest: one signed Node for host and guest, and a stale-Chromium report before each release

未关闭
  • 哪里不对？
#475 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
debian, docker, node.js, rust
领域
build-system, release

调研方向

Start with scripts/build/build-browser-vm-rootfs.sh, scripts/build/stage-browser-vm-target.sh, components.json, and scripts/release-upstream-recipes.json to trace how Node enters the guest image. Then inspect scripts/browser-vm-image-inputs.py and scripts/build/browser-vm-debian-lock.json, plus the release check for the Chromium pin. Done means the guest uses the recipe’s signed Linux Node artifact with its receipt and licence, image inputs change with the pin, and the release check reports pinned and current Chromium versions; validate the installed Browser journey on Apple Silicon.

由索引模型根据 Issue 内容生成。

描述

post-0.8.0

After 0.8.0. Part of #87 (Private Browser). Proposed by Sash on 21 Oct. Facts checked on release train 9f137a469 (21 Oct). Security details stay in private release and security tracking.

Current state

The Browser guest image installs Node from the Debian package set (scripts/build/build-browser-vm-rootfs.sh:297). The guest runs the Selkies control service and the VZ transport bootstrap with it (scripts/build/stage-browser-vm-target.sh:636, :780). The host uses a different Node: the signed release pins it by version and SHA-256 (components.json external.node, scripts/release-upstream-recipes.json). So two Node lines need separate updates, and the guest line follows Debian's schedule.

The guest Chromium packages are pinned by a Debian security snapshot (scripts/build/browser-vm-debian-lock.json). Each refresh changes the guest image inputs, so it needs an image rebuild and a Browser check on a Mac. Today the release owner finds a stale Chromium pin only by comparing it with Debian by hand.

What changes
  • The guest uses the common pinned Node version with the signed Linux artifact for its architecture, built into the image from release-upstream-recipes.json. Darwin hosts retain their signed Darwin artifact at that version. The Debian nodejs package leaves the image.
  • The release check reports how old the guest Chromium pin is against the current Debian security snapshot, so a release owner sees a stale pin before the freeze.
Acceptance criteria
  • The guest image contains one Node at the common pinned version. Its bytes match the signed Linux guest architecture recipe, with the recipe digest, artifact receipt and licence included in the image input closure. Test version and per-platform hash mismatch.
  • Changing the Node pin changes the guest image inputs (scripts/browser-vm-image-inputs.py), so release admission requires a rebuilt image.
  • The release check names the pinned and the current Debian security Chromium versions.
  • On an Apple Silicon Mac, Browser opens, renders a busy news site, plays video with audio, takes typing and clicks, and closes, on the rebuilt image installed by update.

After a shared guest change, each advertised host adapter needs the applicable installed journey on that exact guest. #217 owns release production, #87 owns the Mac journey, #90 owns the Jetson journey, and #293 owns the support verdict.

Owner

Sash (Browser).

主要语言
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 摘要。