Hi, I was referring to this post http://community.spark.io/t/suggested-addition-to-documents-wireless-security/5552 , but I could not come clear with it. So my queries are: If I am not using the Spark Cloud means any connection over TCP ( say MQTT for instance over local wifi) is not secure unle…

Hi @gaurav TLS/SSL has two phases–a certificate-based public key negotiation phase and the data transfer phase using private key crypto like AES. The Spark cloud implements both of these phases by preloading all the Spark cores with the cloud public key and different core-specific private key for n…

I don’t know tls/ssl well at all, although I did have a look at porting one of the open source embedded ssl libraries to the core. Seems they are just a touch too large for the available flash and RAM without some shoehorning to get them down to size. The public certificates could be stored in exte…

So the cert for spark.io is 2032 bytes base-64 encoded so a bit smaller when expanded on the core, but still sizable. Putting the certs in flash (internal or external) is possible but renewable security becomes anywhere from medium hard to impossible. All the root certs changed recently with Heart…

For cert updates, wouldn’t pushing a new cert to flash be sufficient? e.g. via dfu-util?

If using just AES is an option there’s this example code: [image] AES encryption demo and secure TCPClient usage Here’s a little demo that you can paste into Spark Build that shows how to use the AES-128-CBC encryption already available in the Spark Core firmware. Put that on a Core …

And @gaurav , just to be extra clear on both your specific queries—yes, if you are using the built-in TCPClient object to connect to your own server, all communication will be plaintext (not encrypted) unless you specifically implement security yourself.

Hi @zachary Thank you so much for this demo. I am learning AES as I want to secure communication from the spark to my own server. I do not have a deep understanding of AES. I understand that you have data(buf in this demo), a key for encryption(key in this demo), but what is the iv variable? I know…

IV stands for “initialization vector”. AES can be done in several modes. In CBC mode, the key stays the same for the whole session, but the IV changes for every message. Both the key and the IV are used as part of the encryption. You can think of them as forming a composite key that changes for ever…

Implementing security TLS/SSL with no Spark-cloud

Firmware

mdma September 17, 2014, 5:58pm 6

If using just AES is an option there’s this example code:

Topic		Replies	Views
Suggested addition to documents: wireless security Getting Started	8	2362	July 16, 2014
Navigate in core firmware directory? Firmware	3	930	June 12, 2014
AES encryption demo and secure TCPClient usage Firmware	37	14708	October 14, 2016
Onboard Twitter OAuth 2 Library (Looking For) General	8	1712	May 7, 2014
How to send HTTP POST request to a secure URL Cloud	19	13124	September 24, 2015

Implementing security TLS/SSL with no Spark-cloud

Related topics