Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#753 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, go
Domain
release, security

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
12
Forks
14
Avg merge
1d 5h
Merged PRs (30d)
239

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenTollGate/tollgate-module-basic-go

All issues in OpenTollGate/tollgate-module-basic-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.