NRF9160 FOTA over HTTPS

RE: NRF9160 FOTA over HTTPS

fastfox — Thu, 05 Mar 2020 12:16:29 GMT

Yep, thanks. That is pretty much what I have been trying to do for few hours now.

Just struggling with unknown CA problems, even though there is another active TLS connection using the same CA cert while download client TLS fails. But that is another story.

RE: NRF9160 FOTA over HTTPS

Martin Lesund — Thu, 05 Mar 2020 09:53:33 GMT

Hi Fastfox,
Thank you for pointing that out.

By the way, we happily would like contributions to expand our libraries in NCS so that the libraries can be more flexible for your use-case.
(Ther is a Pull request on the User Guide on how developers can contribute to NCS)

There was just pushed out a Pull request based on what you have mentioned:

Add option to define security tag for TLS

If you need more control over how the HTTP requests look like, then
a suggestion is that you could build your own FOTA library based on HTTP_CLIENTand in a combination with the DFU TARGET.

RE: NRF9160 FOTA over HTTPS

fastfox — Wed, 04 Mar 2020 12:50:28 GMT

Hi,

Thanks for prompt reply.

So basically the answer is that I should butcher fota lib to get HTTPS and butcher download client to get the headers, right?

What about the roadmap. IMHO, those libraries should have APIs that can be used to configure such stuff instead of having to fork and rewrite the code.

RE: NRF9160 FOTA over HTTPS

Martin Lesund — Wed, 04 Mar 2020 12:38:26 GMT

Hi Fastfox,

By default, the FOTA download library uses HTTP for downloading the firmware file.

To use HTTPS instead, apply the changes described in the HTTPS section of the download client documentation to the library.