Hardcode md5 for bz*

Question

Hardcode md5 for bz*

Opened this issue 5 years ago · 3 comments

With the proliferation of custom builds of unraid (DVB, nVidia, and the new Ryzen build), unraid needs the md5s of the bz* files hardcoded somewhere (and not on the flash where it's easy to change) so that the diagnostics can tag something as saying that the user is running a custom build.

Not saying that this is currently an issue, but eventually one of the guys making the builds is going to screw up and cause issues that isnt related to unraid itself.

Answer 1 · 2019-09-23T15:02:03.000Z

We've been saving sha256 of all bz files since beginning of 6.8. We could create api call to retrieve those for a given version. I'll add to the laundry list.

Answer 2 · 2019-09-23T17:27:21.000Z

The one on the flash isn't good enough as any of the image guys could simply update it with their own md5.

Answer 3 · 2019-09-23T17:31:32.000Z

Sure but upon boot (or anytime) a function can be run that generates the sha256 of existing bz files and compares against both on-flash and make call to our key-server api endpoint that provides the sha256 of bz files for a given release.