release: sign SHA256SUMS so --upgrade checks where the files come from
I maintainer di solito rispondono entro 2 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
Read .github/workflows/release.yml, server-prep.sh, SECURITY.md, the README, and tests/upgrade.sh. First, resolve the maintainer choice between minisign/signify and GitHub artifact attestations, then trace the existing --upgrade checksum flow. Done when releases provide verifiable provenance, upgrades check it and reject invalid results, the docs explain manual verification, and tests cover valid and invalid signatures.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What
Sign the release checksums, so server-prep.sh --upgrade (and anyone who downloads a release by hand) can check that the files really come from the maintainers, not only that the download is complete.
Why
Today SHA256SUMS is downloaded from the same GitHub release as the scripts, over the same HTTPS connection. It catches a broken or truncated download, and a single swapped file. It does not help when someone can replace files in a release: they can replace SHA256SUMS too (for example with a compromised GitHub account, a stolen release key, or a tampered release run). This is the same trust as a manual download, so nothing got worse, and the docs now say so plainly (raised in the review of exceev-consulting/server-prep#183).
Options
- minisign (or signify): the release workflow (or a maintainer) signs
SHA256SUMSwith a key kept outside GitHub, and the public key is written in the scripts and the README.--upgradechecksSHA256SUMS.minisigbefore anything else whenminisignis installed, and says clearly when it cannot. - GitHub artifact attestations: the release workflow publishes a provenance attestation for each file, and
--upgraderunsgh attestation verifywhenghis present. No key to keep, but it still trusts GitHub itself.
Both change .github/workflows/release.yml, so this needs a maintainer's choice first.
Done when
- A release carries a signature (or attestation) for its files.
--upgradechecks it when the tool is present, refuses a bad one, and says what it checked.- SECURITY.md and the README say how to check a manual download the same way.
tests/upgrade.shcovers a good and a bad signature with the fake release.
- Lingua principale
- Shell
- Stelle
- 2
- Fork
- 3
- Merge medio
- 2g 14m
- PR unite (30g)
- 47
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di exceev-consulting/server-prep
-
area: docs bug claude documentation good first issue priority: low size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
exceev-consulting/server-prep#225 ·
I maintainer di solito rispondono entro 2 giorni
-
area: preconfig bug claude priority: medium size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
exceev-consulting/server-prep#224 ·
I maintainer di solito rispondono entro 2 giorni
-
claude enhancement priority: low size: S
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
exceev-consulting/server-prep#222 ·
I maintainer di solito rispondono entro 2 giorni
-
e2e flake: boot fails on debian-13 when its genericcloud image is missing from SHA512SUMSForse già presa @exceev-claude l’ha presa 1 giorno fa. Apertaarea: ci bug claude priority: high size: S
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
exceev-consulting/server-prep#212 · 2 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
server-audit.sh: flag world-writable directories in /etc such as /etc/dokploy (GHSA-qxjv-6cvh-32c6)Apertaarea: audit claude enhancement panel: dokploy priority: high security size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
exceev-consulting/server-prep#211 ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di exceev-consulting/server-prep
Issue simili
-
bot-found documentation priority: P3
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
madenvel/KalinkaPlayer#602 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
huggingface/kernels#1006 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 94/100
I maintainer di solito rispondono entro 2 giorni
-
severity: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
luainkernel/lunatik#2594 ·
I maintainer di solito rispondono entro 1 giorno