Closed
Description
Hi there,
how do I prevent the http-ota-update from downloading a wrong/invalid firmware file?
Of course there is a MD5 check available. But what about a file-download which get's intercepted/redirected to a kind of malware source? The esp will download the "wrong" file, checks the file integrity with help of MD5 sum and will finally update with the malicious firmware...
Is there a https-example for http-ota-update somewhere?
Has anyone thought about signing the firmware-file? --> would be independant from https/ssl/tls/...
br,
Alex
Metadata
Metadata
Assignees
Labels
No labels