Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

FreedomTechFeed release assets carry no sha256 digests — installer tamper-check has nothing to verify

Aperta
  • Qualcosa non va?
#753 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
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, go
Ambito
release, security

Direzione di ricerca

The issue points to FreedomTechFeed/packages releases and its release-publish.yml; start by inspecting the release upload action or API call and checking the release asset digests with the shown gh release view command. Determine whether updating the publishing tooling supplies digests or whether the job must attach them. Done means published tollgate-wrt assets have verifiable SHA-256 digests; the issue offers an installer E2E for verification.

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

Descrizione

needs:human-review

Migrated from Amperstrand/tollgate-module-basic-go#96 as part of the fork retirement — OpenTollGate/tollgate-module-basic-go is the single source of truth; the fork issue carries the original discussion and any lab evidence. Retirement plan: see the tracking issue linked in the migration comment there.]

What

The FreedomTechFeed/packages releases that publish tollgate-wrt carry no asset digests — every digest field in the GitHub Releases API is null. Checked 2026-09-23:

gh release view v0.6.0-alpha4-pre15 -R FreedomTechFeed/packages --json assets \
  --jq '{assets: (.assets|length), with_digest: ([.assets[]|select(.digest)]|length)}'
# {"assets":14,"with_digest":0}

Same across the whole v0.6.0 pre stream (alpha1 → alpha4-pre15, 20+ releases, spot-checked).

Filed here rather than the feed repo because FreedomTechFeed/packages has issues disabled.

Why it matters

The tollgate-installer downloads tollgate-wrt from these releases and has in-flight work verifying the asset sha256 against the release-reported digest before installing to a router. With digests absent, that verification can only warn-and-proceed — a corrupted or tampered feed asset installs silently. This surfaced as a gap in the 0.6.0 state film (2026-09-20 and 2026-09-23 runs): https://blossom.primal.net/5f3219db93fbfaa5a96b834ed64dcec172c95cee9d19c4b5bb070a3ebd13814f.html

Fix options

  1. GitHub auto-populates the asset digest field for releases uploaded through current tooling — if the feed's release-publish.yml upload action/API call predates that, bumping it may be the whole fix.
  2. Or compute digests in the publish job and attach them (release-body table or API digest) so consumers have an authoritative value.

Verification offer

We have an automated installer E2E (fresh OpenWrt VM → wizard → feed package → branded router, 3/3 green) that can assert digests as soon as a release carries them.

Lingua principale
Go
Stelle
12
Fork
14
Merge medio
1g 8h
PR unite (30g)
201

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 OpenTollGate/tollgate-module-basic-go

Tutte le issue di OpenTollGate/tollgate-module-basic-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.