The use of tInsecure() is, obviously, insecure.
Since the fingerprints change yearly, this means the fingerprint will have to be re-extracted and the code recompiled each time a fingerprint changes. Fingerprints require the user to know exactly which pages the ESP will connect to and extract the Fingerprints from each of those websites. The normal ways to do HTTPS with an ESP8266 is to either use Fingerprints, or to use tInsecure(). wrote in to let us know he’s been working on a way to make HTTPS requests easier to do on ESP devices.
Off the shelf devices often have terrible security while DIY solutions can be complicated, needing recompilation every time a website’s fingerprint changes. Security has always been an issue with IoT devices.
