dasrecht / deye-firmware

141 stars 14 forks source link

Incorrect digest #1

Closed fungs closed 1 year ago

fungs commented 1 year ago

I downloaded the files today and got different digests.

shasum *.bin
ec17ee0a15d1931b0475ab1192506d2584127c82  MW3_15U_5406_1.471.bin
576eaf8d6d7ffee53812d59dda839fc832c37fc6  MW3_16U_5406_1.53.bin
LC_ALL=C stat *.bin
  File: MW3_15U_5406_1.471.bin
  Size: 438282      Blocks: 0          IO Block: 4096   regular file
Device: 3ch/60d Inode: 1362        Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/     user)   Gid: ( 1000/     user)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2023-01-24 13:36:43.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
 Birth: -
  File: MW3_16U_5406_1.53.bin
  Size: 446429      Blocks: 0          IO Block: 4096   regular file
Device: 3ch/60d Inode: 1363        Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/     user)   Gid: ( 1000/     user)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2023-01-24 13:37:40.000000000 +0100
Change: 1970-01-01 01:00:00.000000000 +0100
 Birth: -
dasrecht commented 1 year ago

I used sha256 for the Digest files. If you run

shasum -c MW3_15U_5406_1.471.bin.DIGEST
shasum -c MW3_16U_5406_1.53.bin.DIGEST

you should get back an OK for the shasums

dasrecht commented 1 year ago

But running shasum normally i get the same outputs :)

fungs commented 1 year ago

You are right, my bad. I was naively assuming that the strings would be the same but I probably missed some detail here.