Image SHA256 checksum mismatch
- Dominant language
- No language data
- Stars
- 496
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
I get a diiferent hash key between the CB1 Klipper image and the provided sha256 key. I tried to download the image 3 times to make sure but they all seem to provide the same incorrect hashkey. Also this image doesn't seem to work in my sd card so probably something is wrong
#~/Downloads$ sha256sum CB1_Debian12_Klipper_kernel6.6_20241219.img.xz
eff1412d4525c1ce9c6fe7135a771b2c507bfda5caf595a2b22735b68ebb9b24 CB1_Debian12_Klipper_kernel6.6_20241219.img.xz
#~/Downloads$ more CB1_Debian12_Klipper_kernel6.6_20241219.img.sha256
f9d9143bcb47ad6bd859c24eb9f06093385b9957d89e6493e520c401150584d7
can someone take a look at it please and verify.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the downloaded CB1_Debian12_Klipper_kernel6.6_20241219.img.xz with the value in CB1_Debian12_Klipper_kernel6.6_20241219.img.sha256 using sha256sum. Verify whether the published checksum or image is incorrect, and consider the SD-card boot report when confirming the corrected release artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian
- Domain
- operating-systems, release
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100