Checksum Verification for nRF BLE Stack Downloads
Description
The download script for the nRF BLE stack does not perform checksum verification of any of the downloads. Obviously the checksums would have to be updated every time we bump the stack versions needed, but this could add some extra safety against, for instance, botched downloads.
In addition, much of the bash code is duplicative, and could be refactored.
Code Size
As the sha256sum etc commands are part of coreutils, I do not see this adding any additional dependencies, plus the refactoring should result in less code size / maintenance costs.
Implementation
I intend to implement this feature and would submit a Pull Request if desirable
Code of Conduct
Yes, I agree
nrf/drivers/bluetooth: Change soft-device download URL to self hosted.
Summary
The existing URLs have started to return a HTTP 403, breaking CI, among other things. The simplest way around this is to host the files at micropython.org, and point to them from the download script.
The soft-device files have been retrieved from:
- https://www.nordicsemi.com/Products/Development-software/s110/download
- https://www.nordicsemi.com/Products/Development-software/s132/download
- https://www.nordicsemi.com/Products/Development-software/s140/download
Testing
Tested locally. Will also be tested by CI.
Trade-offs and Alternatives
There may be a URL maintained by Nordic (eg on GitHub) for these files, but it seems the most robust thing to do is self-host them.