INSTEON is leading the way in the field of home automation and control technology with a line of products that include a wide range of smart home devices such as lighting, motion detectors, and security systems. All INSTEON products can be centrally accessed through the Hub, a product that has the ability to connect the smart home even when the network is down.
While researching the best SSL/TLS library for securing the Hub, INSTEON found wolfSSL’s CyaSSL as the optimal solution. With its portable and lightweight design, CyaSSL was seamlessly integrated into INSTEON’s Hub, providing INSTEON users with a safe and secure network to manage all of their smart home devices.
To learn more about INSTEON and their wide range of devices, feel free to visit their website. The INSTEON/wolfSSL case study can be viewed on our Case Studies page.
For questions regarding the use of wolfSSL products in your embedded or IoT devices, contact us at email@example.com.
The next release of CyaSSL will have official support for the PicoTCP TCP/IP stack. wolfSSL has been working closely with the developers at TASS to add out-of-the-box support for this new, lightweight, and dual-licensed TCP/IP stack – making it easier to secure Internet of Things devices running on top of PicoTCP.
For those not familiar with PicoTCP, it is “a TCP/IP stack developed from the ground up for embedded devices, by embedded software engineers. Resource usage, modularity and portability to different hardware platforms and embedded operating systems are key.” Like CyaSSL, PicoTCP is open source and dual licensed under both the GPLv2 and a commercial license.
TASS has put together a helpful demo application using both CyaSSL and PicoTCP, with a walkthrough documented here:
When compiling CyaSSL for use with PicoTCP, users will need to define CYASSL_PICOTCP, and optionally CYASSL_PICOTCP_DEMO when compiling for use with the example demo application listed above.
If you are interested in using CyaSSL with PicoTCP, or have any questions, please contact us at firstname.lastname@example.org.
TASS Belgium: http://www.tass.be
Hi! We’ve been telegraphing our plans to drop support for SSL 3.0 for the last year. With the emergence of the POODLE breach, we’ve decided to accelerate our plan. Over the coming weeks and months, we’ll be doing the following:
1. Disabling SSL 3.0 by default at runtime.
2. Disabling our SSL 3.0 code by default at compile time.
3. Eliminating all SSL 3.0 code from our code base, and using TLS 1.0 as the base.
If you have comments or questions, then feel free to contact us at email@example.com or call us up at +1 425 245 8247.