Add Release Hashes to Website
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This is not really a bug of the code. This is a feature request on the website. Please move this information to the correct location.
The feature request for the instructions on how to verify the download of the installation files. I am specifically looking for SHA256 hash for the windows installer, keybase_setup_386.exe.
I see that this file is signed with a Digital Signature, but I am not savvy enough to verify this signature independently. I have viewed the details of the Digital Signature, but none of the details match the SHA256 of keybase_setup_386.exe. So either I've got a bad file, or I'm doing something wrong.
Please either listing the SHA256 hashes in a signed text file or some instructions on independent verification of the installer files.
Thank you for the great application!
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 at the website's download or installation-verification entry point and inspect how keybase_setup_386.exe is published and signed. No repository file or test is named in the issue. Done means the website provides SHA256 hashes in a signed location or clear independent-verification instructions for installer files.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100