[Feature]: Publish signed binaries
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 152
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 11
Description
Suggestion Description
Please consider signing the binaries, especially now that the project is under the ROCm umbrella.
I was a bit confused because it's something that you yourself pledge in the copy/documentation on the website but at least the .msi isn't actually signed unless i'm missing something?
Thanks for the tool btw, works a treat.
Operating System
No response
GPU
No response
ROCm Component
No response
Contributor guide
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 locating how FastFlowLM currently builds and publishes its .msi and other binaries, then check where signing would fit in that release process. Done means the published binaries are verifiably signed and the website documentation accurately reflects their signing status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devops, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100