ScruffR
September 25, 2018, 9:46am
4
I'd not go down that rabbit hole.
There are some libraries that tried to leverage secure connetions for user applications with Particle devices but they are (often) cumbersome to use and rather heavy on the memory of the device.
The simplest way will either be to change your server to accept HTTP or go for webhooks.
some links
Hey Community,
We have been working hard at glowfi.sh to deliver an HTTPS client for the Particle community and I am happy to say we are ready to release it thanks to all the work by glowfi.sh engineer @jersey99 . Our client is built from matrixSSL, and you can check out our documentation, specs, and examples in our glowfishAPI repo for Particle here .
Again, we are super excited to release this and welcome any comments, feedback, pull requests, etc.!
Thanks
Mike and the glowfi.sh Team
Sign u…
This port is about 90% done. I am soliciting any helpers at this point.
I am using the mbedTLS/TlsTclClient library as a template. The main goal of this is to get https://things.ubidots.com working. I have tried a myrad of compile combinations with the old and the development version of mbedTLS. It will connect to many other https sites but not the Ubidots site. Plain unix curl works fine so, these libraries should work as well.
I just wanted to give a shout out that there is a work…
Hi,
I’m working on getting WolfSSL up and running for Photon/P1, but I keep running into problems that I’m having a hard time solving. They have a really good guide for how to do this and I’ve solved most of the configuration issues up until now.
I don’t have anything that works yet though and I’m suspecting this has to do with the fact that WolfSSL is C and the Particle compiler have a preference for CPP? I’m pretty sure that the error above indicates a larger problem (unknown type name ‘clas…
1 Like