wolfSSL with Keil MDK5 and RTX

If you are a Keil MDK-ARM user, we’re happy to remind our users that the wolfSSL embedded SSL library is integrated into the Keil MDK5 as an easy-to-use software pack.

This integration means that MDK5 users can easily pull in SSL/TLS support directly to their Keil projects without going out to the web to do a separate download.  In addition to the library itself, several example projects using wolfSSL are also available.

As stated by Reinhard Keil, ARM’s Director of MCU Tools, “The Keil and wolfSSL teams have successfully collaborated to fully integrate wolfSSL Embedded SSL into MDK 5. The result is the most seamless tool combination available for developers wishing to secure their device communications with SSL.”

To read more, the press release can be found here: http://www.prweb.com/releases/2013/10/prweb11215195.htm.  We’re excited to hear user feedback and field any questions that may come up.  Let us know what you think at info@wolfssl.com.

wolfSSL also supports Keil RTX.  Keil RTX is a Real-Time Operating System (RTOS) that supports ARM and Cortex-M.  It is a royalty free RTOS designed for embedded systems with deterministic behavior.  Read more about Keil RTX here: http://www.keil.com/rl-arm/kernel.asp and http://www.keil.com/rl-arm/rtx_benefits.asp

Documentation for wolfSSL with Keil MDK-ARM can be found here: https://www.wolfssl.com/docs/keil-mdk-arm/

Intel Quick Assist and wolfSSL

wolfSSL has begun adding support for the Intel Quick Assist 8950 PCIe adapter. By utilizing our new asynchronous support and the quick assist’s cryptography acceleration we should yield performance many times better than what can be achieved in software alone. This adapter retails for about $800 and is capable of 40K RSA 2048-bit operations per second. If you’d like more information please contact info@wolfssl.com.

Product Brief: http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/quickassist-adapter-8950-brief.pdf

New FIPS Operating Environments

wolfSSL fans! Do you like FIPS? Do you like virtual machines? Guess what. wolfSSL`s crypto library, wolfCrypt, has been validated for FIPS 140-2 mode running on three different virtual operating environments. We now have wolfCrypt validated for Microsoft® Windows® 7 running on VMware ESXi™ and SUSE® Linux Enterprise Server running on both VMware ESXi™ and Microsoft® Hyper-V®. If you are interested in getting a FIPS 140-2 approved crypto library running in your virtual operating environment, or any operating environment, please don`t hesitate to send us an email at fips@wolfssl.com. We look forward to hearing from you.

Upcoming Whitewood Webinar: Three Critical Steps to Maximize Crypto Security

One of wolfSSL’s partners, Whitewood, is holding a webinar next Tuesday (June 28, 2016) at 12:00pm EST. They will be talking about the importance of random numbers and ways to generate entropy:

Three critical steps to maximize crypto security
When: June 28, 2016, 12:00pm EST
Presenter: Richard Moulds, Vice President, Whitewood

If you are interested in attending the webinar, you can register at the following URL:

https://www.brighttalk.com/webcast/13385/212435

wolfSSL Version 3.9.6 Released!

Many new additions and updates have been introduced in wolfSSL 3.9.6. For IoT and embedded SSL/TLS there was the addition of embOS and uTasker ports, each of these ports allowing for easily building wolfSSL on the respective environments. Updates were also done to STM32 crypto for using AES-GCM and AES-CCM, and updates were made to the MDK5 projects.

AES-NI saw an update for AES-CBC decrypt with wolfSSL version 3.9.6. This update decrypts 6 or 8 blocks at a time, greatly speeding up decryption times while using AES-NI. Additions that overlap both IoT and desktop platforms were also added like the addition of static memory. Compiling wolfSSL with –enable-staticmemory allows for using no dynamic memory while creating a SSL/TLS connection. This is useful for applications that wish to have a fixed amount of memory ahead of time and want more control over memory management. In addition to using static memory, compiling with –enable-sessionexport allows for serializing and exporting DTLS session information after the handshake is completed – giving the option of performing DTLS handshakes on one device and then sending that connection over to another device to handle throughput.

wolfSSL`s wrapper and OpenSSL compatibility layer were both expanded with the recent release. Version 3.9.6 introduced Python wrappers for crypto operations, allowing for integrating wolfSSL in Python projects. This easy to build wrapper is found in the directory “wolfssl-3.9.6/wrapper/python” along with a set of instructions for building it. Expansion to the OpenSSL compatibility layer was made with the introduction of dynamic session tickets. This makes it even easier for plug and replace when switching to use wolfSSL.

Furthering the progressiveness of wolfSSL, there was the addition of using the netRandom quantum random number generator from Whitewood. Now a quantum resistant cipher suite using NTRU can also be using a quantum random number generator. Making wolfSSL an excellent choice for quantum resistant security.

If looking to gain more speed with SSL/TLS connections operating in parallel to each other, check out the asynchronous operations addition to wolfSSL with this version. This keeps wolfSSL from blocking on SSL/TLS operations, such as RSA for example, in addition to non blocking on socket read/writes. If interested in using the new asynchronous features of wolfSSL please contact info@wolfssl.com.

Along with all the additions and updates, some fixes were made to wolfSSL code with release 3.9.6. One fix was some edge case bugs with ECC when using ALT_ECC_SIZE and with key sizes over 256 bits. Additional code and comments on these ECC fixes can be found on our github page with pull requests #411, #416, and #428. The following list shows highlighted feature additions, updates and fixes.

Expanded list of release 3.9.6 for wolfSSL including new features and bug fixes:

– Add staticmemory feature, for using no dynamic memory allocation with wolfSSL
– Add public wc_GetTime API with base64encode feature
– Add AES CMAC algorithm, enabled using –enable-cmac
– Add DTLS sessionexport feature to serialize and send connection information. This allows for another system to take up the connection after the DTLS handshake has been performed
– Add python wolfCrypt wrapper. Located in directory wolfssl-3.9.6/wrapper/python.
– Add ECC encrypt/decrypt benchmarks. Can be ran with “./configure –enable-eccencrypt –enable-hkdf && make && ./wolfcrypt/benchmark/benchmark”
– Add dynamic session tickets to be used with openSSL compatibility
– Add eccshamir to configure.ac giving the option to compile without using ECC_SHAMIR. Can be used with ./configure –disable-eccshamir
– Add quantum RNG support with Whitewood netRandom, –with-wnr
– Add embOS port. Located in the directory wolfssl-3.9.6/IDE/IAR-EWARM/embOS
– Add minimum key size checks for RSA and ECC during TLS connection
– Add STARTTLS support to example client with ‘-M’ argument
– Add uTasker port. Macro define for uTasker can be found in wolfssl-3.9.6/wolfssl/wolfcrypt/settings.h
– Add asynchronous crypto and wolf event support
– Add compile check for misc.c with inline, this helps developers working in IDEs to not compile misc.c when not needed
– Add RNG benchmark to wolfcrypt/benchmark/benchmark.c
– Add reduction to stack usage with hash-based RNG
– Update STM32F2_CRYPTO port with additional algorithms supported, AES-GCM and AES-CCM
– Update MDK5 projects
– Update AES-NI to allow decrypting AES-CBC by 6 and 8 blocks at a time
– Fix for STM32 missing wc_ShaUdate return code with STM32F2_HASH defined
– Fix for function visibility warnings when building with MinGw
– Fix ECC math bugs with ALT_ECC_SIZE and key sizes over 256 bit. Code changes for ECC fix can be found at pull requests #411, #416, and #428
– Fix mismatch of certificate buffers to certificate files, github issue #422
– Fix decrypt max size with RSA OAEP. Previously in the case that the max message size allowed was being decrypted a bad padding error was returned
– Fix DTLS sanity check with DTLS timeout notification
– Fix free of WOLFSSL_METHOD on failure to create CTX
– Fix potential memory leak in failure case with wc_RsaFunction. Builds using RSA with using normal math and not RSA_LOW_MEM should update

Note: the tag v3.9.6w is for a simple port value fix with the echo server on a windows OS. This is with using Visual Studio as a development and testing environment.

For more information about any of the items on this list or information in general about wolfSSL contact us at info@wolfssl.com

New Cipher Suite, ECDHE-ECDSA-AES128-CCM

In the interest of supporting the lightweight cipher suites used in the IoT, wolfSSL has added ECDHE-ECDSA-AES128-CCM. This is an AEAD cipher suite with the perfect forward secrecy that ECDHE provides, using AES128 counter mode to encrypt the data and provide the 16-byte MAC. If there are any new ciphers or cipher suites you would be interested in having support for in the wolfSSL embedded SSL/TLS library, let wolfSSL know at info@wolfssl.com.

wolfMQTT v0.8 (06/13/16)

We’ve added an Azure IoT Hub example to wolfMQTT in the v0.8 release. For this example we setup an Azure cloud server to demonstrate the IoT Hub. This example demonstrates how to connect/authenticate (creation of a SasToken), how to publish events and how to listening for device bound messages.

Release Notes:
* Fixed stdin capture bug and improved signal (ctrl+c) handling.
* Added Azure IoT hub MQTT client example.
* Added support for MQX / RTCS.
* Added “–disable-tls” and “–disable-examples” configure options.
* Added comment about max packet size.
* Added example for how to load a client certificate to mqttclient example.
* Added return code for firmware and azure examples that are not compiled in due to older / incompatible version of wolfSSL.
* Moved the support for custom printf/line endings into the mqtt_types.h for use throughout the project.
* Updated README.md with information about the examples.

If you have any questions about wolfMQTT or the wolfSSL embedded SSL/TLS library, contact us at info@wolfssl.com

Using wolfSSL from the Swift Programming Language

The Apple Worldwide Developers Conference (WWDC) is currently underway in San Francisco, CA this week. One of the conference topics, also mentioned in the Keynote, is the Swift programming language.

Swift, introduced roughly two years ago, is a programming language for macOS, iOS, watchOS, and tvOS that is gaining popularity with developers. This year at WWDC, several announcements were made including the introduction of the Swift Playgrounds app for iPad.

We would like to ask our user base if there is any interest in a Swift wrapper for the wolfSSL embedded SSL/TLS library. wolfSSL currently has language wrappers for Java, C#, and Python, and is generally portable across devices and operating systems. Are you interested in using wolfSSL from Swift? If so, let us know at info@wolfssl.com!

WWDC16
Swift Programming Language (Apple)

wolfSSL at NXP FTF 2016 with Embedded Computing Design

During the NXP FTF 2016 conference in Austin, TX last month, Brandon Lewis from Embedded Computing Design stopped by the wolfSSL booth. He talked with Chris Conlon about how the wolfSSL embedded SSL/TLS library enables secure communication on embedded, resource-constrained devices.

To listen to the interview, follow the link below to Slide 7 of Brandon’s “Floored: NXP FTF 2016” article:

http://embedded-computing.com/28205-floored-nxp-ftf-2016/?slide=7

wolfSSL with PikeOS and ElinOS

We were recently reading about PikeOS and ElinOS, embedded operating systems from SYSGO AG and were curious if any wolfSSL users are interested in the wolfSSL embedded SSL/TLS library and wolfCrypt cryptography libraries running on these operating systems.  If you aren’t familiar with these operating systems, here’s a quick summary via Wikipedia:

PikeOS:

“PikeOS is a microkernel-based real-time operating system made by SYSGO AG. It is targeted at safety and security critical embedded systems. It provides a partitioned environment for multiple operating systems with different design goals, safety requirements, or security requirements to coexist in a single machine.”

ElinOS:

“ELinOS is a commercial development environment for embedded Linux. It consists of a Linux distribution for the target embedded system and development tools for a development host computer. ELinOS provides embedded Linux as a standalone operating system or it can be integrated into the PikeOS virtualization platform if safety and security demands cannot be met by Linux alone.”

If you are interested in seeing support in wolfSSL for these OS’s, let us know at info@wolfssl.com!

Posts navigation

1 2