RT-AC87U: 384.13_10 - SHA256 signatures?

[user808]

Hi,

could someone tell me where I can find the SHA256 signatures for release 384.13_10, please? The release is available, but has no SHA256 signature listed on the official site.

Thanks.

 

[L&LD]

Look in the zip file you downloaded.

 

[dave14305]

Look in the zip file you downloaded.

Valid, but one shouldn’t necessarily trust a signature published at the same place as the file being verified if you’re looking to establish authenticity. If a bad guy can alter the zip, he can alter the included SHA signature as well. Better to have the signature verified from a separate site (like Asuswrt-Merlin.net) since it would be harder to compromise both locations.

 

[L&LD]

Agreed, but I would like to think it was downloaded from the official site.

 

[RMerlin]

Agreed, but I would like to think it was downloaded from the official site.

There are no downloads on my website. They are stored on Sourceforge and Onedrive. That's why I post SHA checksums on my website, since it's completely separate.

 

[L&LD]

Thank you both gentlemen for the clarification.

 

[dave14305]

There are no downloads on my website. They are stored on Sourceforge and Onedrive. That's why I post SHA checksums on my website, since it's completely separate.

Should there be signatures listed for the 384.13_10 models then?

 

[RMerlin]

Should there be signatures listed for the 384.13_10 models then?

They are gone because my deployment script overwrote them when I released 384.19 (the page is dynamically generated from a data file pushed to the web server on new firmware deployment).

The new website I'm working on has a separate section for EOL models which will list the final hashes for these models, so they don't get overwritten when publishing new releases.

For now, here they are:

0cae8e78a735bb584ef1248c455e88bb3725a76cbf7fc7402cd4a9db39f3a37a  RT-N66U_380.70_0.trx
f78d95ae1e56e9cb80d94451948e91fa9868a8afda993bdd4d2ea3a6b6710b77  RT-AC66U_380.70_0.trx
15e89389a7668841e405bed7a36b232e65f7c81ec9f3d107aa56868fa9d32ae5 RT-AC56U_384.6_0.trx
8931f836b1d482b961a1c3ff641fb2bc40c08a838fa0a39dad0f25c05e13f65e RT-AC87U_384.13_10.trx
c641f3a45fd84a7994e1fce187893a8ed49f0f5ad516964ada3e52445c4bc687  RT-AC3200_384.13_10.trx

 

[user808]

Thank you all for the replies and for providing the signatures. This will allow me to eek a little more life out of my old router

 

[user808]

They are gone because my deployment script overwrote them when I released 384.19 (the page is dynamically generated from a data file pushed to the web server on new firmware deployment).

The new website I'm working on has a separate section for EOL models which will list the final hashes for these models, so they don't get overwritten when publishing new releases.

For now, here they are:

0cae8e78a735bb584ef1248c455e88bb3725a76cbf7fc7402cd4a9db39f3a37a  RT-N66U_380.70_0.trx
f78d95ae1e56e9cb80d94451948e91fa9868a8afda993bdd4d2ea3a6b6710b77  RT-AC66U_380.70_0.trx
15e89389a7668841e405bed7a36b232e65f7c81ec9f3d107aa56868fa9d32ae5 RT-AC56U_384.6_0.trx
8931f836b1d482b961a1c3ff641fb2bc40c08a838fa0a39dad0f25c05e13f65e RT-AC87U_384.13_10.trx
c641f3a45fd84a7994e1fce187893a8ed49f0f5ad516964ada3e52445c4bc687  RT-AC3200_384.13_10.trx

The signature contained in the download from sourceforge and the signature returned from a check run from my machine shows "06b7d1d52c81519797cb19d61aa9345a33ce06e5badd4ca5e466cf86eb629cf4" for " RT-AC87U_384.13_10.trx". This doesn't match what you have posted. Am I mistaken some where?

 

[RMerlin]

The signature contained in the download from sourceforge and the signature returned from a check run from my machine shows "06b7d1d52c81519797cb19d61aa9345a33ce06e5badd4ca5e466cf86eb629cf4" for " RT-AC87U_384.13_10.trx". This doesn't match what you have posted. Am I mistaken some where?

Looks like that hash was from a different build, the one from inside the zip file instead of inside my local build directory shows that 06b hash, and a different build timestamp.

 

[user808]

Looks like that hash was from a different build, the one from inside the zip file instead of inside my local build directory shows that 06b hash, and a different build timestamp.

Thats not so good. Doesn't that mean there's no way to prove it come from you and has not been tempered with since the original build?

 

[RMerlin]

Thats not so good. Doesn't that mean there's no way to prove it come from you and has not been tempered with since the original build?

The new website that's under development does have the correct hashes, I was merely explaining why those that I posted weren't correct. These should be the correct ones, although I didn't double check them.

0cae8e78a735bb584ef1248c455e88bb3725a76cbf7fc7402cd4a9db39f3a37a  RT-N66U_380.70_0.trx
f78d95ae1e56e9cb80d94451948e91fa9868a8afda993bdd4d2ea3a6b6710b77  RT-AC66U_380.70_0.trx
15e89389a7668841e405bed7a36b232e65f7c81ec9f3d107aa56868fa9d32ae5 RT-AC56U_384.6_0.trx
06b7d1d52c81519797cb19d61aa9345a33ce06e5badd4ca5e466cf86eb629cf4 RT-AC87U_384.13_10.trx
88158a807cb5d6a23e783a496c7122c29887c7828c00244765a2b22a46e2df96 RT-AC3200_384.13_10.trx