CrowdStrike / CrowdStrike/scoop-foundry-cli
foundry hash check failed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 2
- Avg merge
- 4m
- Merged PRs (30d)
- 2
Description
Scoop output
Installing 'foundry' (1.4.5) [64bit] from 'foundry' bucket
foundry_Windows_x86_64.zip (8.7 MB) [======================================================================================================================================================] 100%
Checking hash of foundry_Windows_x86_64.zip ... ERROR Hash check failed!
App: foundry/foundry
URL: https://assets.foundry.crowdstrike.com/cli/latest/foundry_Windows_x86_64.zip
First bytes: 50 4B 03 04 14 00 08 00
Expected: 05d60b11f6e307579c9d5022bf69619bf330c08dd928532ff028d8ac39a3cbd6
Actual: 0292e4eac01f521c6e1cc98e57d6e6c1f03afb150539eabc4e48ceb9ea1b3692
Manually verified with Posh's get-filehash
Get-FileHash "C:\Users......\Downloads\foundry_Windows_x86_64.zip"
Algorithm Hash Path
SHA256 0292E4EAC01F521C6E1CC98E57D6E6C1F03AFB150539EABC4E48CEB9EA1B3692
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
Locate the Scoop manifest for foundry and compare its recorded SHA256 value with the actual hash in the report. Verify the download source and update the manifest only if the new checksum is confirmed, then test the installation to ensure Scoop accepts the archive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100