...I guess that the code for HTTPS just does not fit into the available space... and even if it would fit, it would hamper the intended work of the core processor which should not be tied up with doing encryption/decryption.
Therefore, 'cheap'/simple comm-devices just are not a solution. For Wifi behind a DMZ with target nodes behind the DMZ, CC3000 or any other WPA2 security supporting system would though be good enough. But in such a case, why would that need authentication, because eaves dropping would have to be on the wire. (For most secure/safe communication, systems behind the DMZ communicate also over HTTPs.)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
...I guess that the code for HTTPS just does not fit into the available space... and even if it would fit, it would hamper the intended work of the core processor which should not be tied up with doing encryption/decryption.
Therefore, 'cheap'/simple comm-devices just are not a solution. For Wifi behind a DMZ with target nodes behind the DMZ, CC3000 or any other WPA2 security supporting system would though be good enough. But in such a case, why would that need authentication, because eaves dropping would have to be on the wire. (For most secure/safe communication, systems behind the DMZ communicate also over HTTPs.)