Sign Build Index Files
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 276
- Forks
- 68
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 14
Description
The erlef/setup-beam Action currently has no way to check authenticity of the downloaded builds. It could theoretically read the SHAs from the builds.txt, but since that is delivered using the same domain, that would add little protection.
Usually I would now recommend to setup actions/attest, but since bob builds outside of GitHub, that does not work.
One solution would be to sign (GPG / RSA or something) the builds.txt with a known keypair. That way clients can check the builds.txt signature, read the SHAs and therefore also trust the builds themselves.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how bob publishes builds.txt and how the erlef/setup-beam Action consumes it. Compare the proposed GPG or RSA signature approach with actions/attest, then define verification using a known keypair. Done means clients can validate builds.txt before trusting its SHAs and downloaded builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, github-actions
- Domain
- build-system, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100