Install ElastOS from a signed release packed inside a desktop installer
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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-installto this repository as a pull request againstdevelop, 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.
- Lenguaje dominante
- Rust
- Estrellas
- 6
- Forks
- 2
- Merge medio
- 1 d 3 h
- PR fusionados (30 d)
- 42
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de elastos/elastos-runtime
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastos/elastos-runtime#563 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
elastos/elastos-runtime#508 ·
Los mantenedores suelen responder en 1 día
-
Documents: Markdown preview web links go through Home's confirmed link flow (#430 follow-up)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastos/elastos-runtime#436 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
elastos/elastos-runtime#427 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
elastos/elastos-runtime#405 ·
Los mantenedores suelen responder en 1 día
Todos los issues de elastos/elastos-runtime
Issues similares
-
bug good first issue help wanted linux macos testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
area: app type: test
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
storytold/photocraft#12706 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug priority-low to-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
examples/dca and limit-order: swap always fails on the real Soroswap router (deadline equals now)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
sorocon-labs/sorocron#172 ·
Los mantenedores suelen responder en 1 día