B4R Question Code Copying via OTA

[RJB]

Something that occurred to me when thinking about OTA updates using an HTTP download such as: https://www.b4x.com/android/forum/threads/esp32-ota-update-from-server-via-wifi-only.149206/.
Could this lead to copying of your 'product'?
i.e. if you are using standard hardware (or even proprietary hardware, which is fairly simple to copy) someone could buy (or copy) the hardware, then download the firmware, load it to the hardware and have a clone of the product?

 

[peacemaker]

I guess, if functions of firmware depends on some your web-host - it will be difficult to clone the server side.

 

[RJB]

That's true but I have a couple of products that can run stand-alone. I think I should look at encrypting the OTA download!

 

[peacemaker]

at encrypting the OTA download

1) see my prev variant https://www.b4x.com/android/forum/threads/esp32-ota-update-from-server-via-wifi-only.149206/ and save decrypting .bin to SPIFFS file first, before update.

2) what about download the non-encripted .bin via HTTPS only, but with some basic authentication ?