Release signing page references wrong file as signature
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 327
- Forks
- 653
- PR merge metrics
- No merged PRs in 30d
Description
Release signing page says:
In a genuine release archive you expect to find the
syncthingbinary (syncthing.exeon Windows) and an accompanying signaturesyncthing.sig(syncthing.exe.sigon Windows)
But lib/upgrade from syncthing/syncthing actually uses release.sig for every OS:
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
Open the release signing page and compare its archive-signature description with lib/upgrade/upgrade_supported.go at the linked upstream line. Update the documentation so the referenced signature filename matches the implementation for all operating systems, then verify the page renders correctly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100