Release integrity: sign SHA256SUMS; checksums today come from the same release

Aperta
#279 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, rust, shell
Ambito
release, security

Direzione di ricerca

Start by reading crates/atlas-cli/src/commands/release.rs (lines 15-45) to see how the .sha256 asset is fetched and trusted, then the checksum-only check at desktop_linux.rs:150 and the unsigned SHA256SUMS/manifest.json writes in release.yml (710-716). The public-key embedding also touches install.sh, and docs/release.md needs the rotation section. Done means the two acceptance bullets pass: a tampered asset with a matching .sha256 is rejected by atlas update, atlas desktop and install.sh, and the workflow signs. Note this is a design decision (minisign vs cosign keyless) that should be agreed with maintainers before coding.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: ci area: installer priority: 2 normal status: confirmed type: feature

Linux roadmap item (tracking: #289). Evidence is from reading code at main (9c32731) and a hand test on Omarchy (Arch, Hyprland Wayland, AMD 680M, Mesa 26.2.5, AppImage 1.5.0-alpha.25). [INFERENCE] marks anything not observed directly.

Problem

crates/atlas-cli/src/commands/release.rs:15-45 downloads <asset>.sha256 from the same GitHub release it verifies; release.yml:710-716 writes unsigned SHA256SUMS/manifest.json; desktop_linux.rs:150 checks ELF magic only. A swapped release or compromised account passes every check (CLI update, install.sh, AppImage sync).

Proposal

Sign SHA256SUMS with minisign (or cosign keyless); embed the public key in the CLI and install.sh; verify before trusting any checksum. GitHub attestations are a complement, not a replacement (install.sh must not need gh). Document rotation.

Acceptance

  • A tampered asset with a matching .sha256 is rejected by atlas update, atlas desktop and install.sh.
  • Release workflow signs; key rotation documented in docs/release.md.
Lingua principale
Rust
Stelle
3
Fork
1
Merge medio
9h 51m
PR unite (30g)
310

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codeatlasdev/atlas

Tutte le issue di codeatlasdev/atlas

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.