Mismatch SHA265 hash?

Software
1

The SHA256 file says the hash for “debian-12-base-arm64+roc-rk3328-cc.img.xz” should be:
be6840d5fd717188f5ad88c22d0700cb21f2fb2aa1b875df972c8da476e947c22d

Windows certUtil:
SHA256 hash of debian-12-base-arm64+roc-rk3328-cc.img.xz:
b57f643622fb5885ab21745bb87e099a2d995886cc0e18ac14ec971b965d48cb

They don’t match? Did I do something wrong?

2

On the SHA256SUM file in Index of /ci/debian/12/

It’s showing 6840d5fd717188f5ad88c22d0700cb21f2fb2aa1b875df972c8da476e947c22d for that specific image.

3

There’s a syncing error between our server and the S3 bucket we’re using. It should be resolved in 24 hours.

4

You’re right, somehow, I copied a wrong SHA hash.

The hash in my file matches yours.

6840d5fd717188f5ad88c22d0700cb21f2fb2aa1b875df972c8da476e947c22d

but I’m still getting
b57f643622fb5885ab21745bb87e099a2d995886cc0e18ac14ec971b965d48cb
from Windows certUtil.

I will check back in 24 hours.

Thanks!

5

It should work now. Our s3 sync wasn’t updating the SHA256SUMS file.

6

Hashes are matching now! Thanks!!

7

Thanks for reporting. We have also updated libretech-flash-tool to verify checksums.