RECENT BLOG NEWS

Hi! This note is to announce that we will be FIPS 140-2 validating our cryptography library, wolfCrypt, on the FreeRTOS platform. If you need FIPS validated crypto on FreeRTOS, let us know at facts@wolfssl.com.

For those of you who have been following our FIPS progress, we are now in the “Review Pending” phase.  See:  http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf (this link is out of date and obsolete, as wolfCrypt now has 2 FIPS validation certificates – #2425 and #3389)

A block cipher is an encryption method that applies a deterministic algorithm along with a symmetric key to encrypt a block of text, rather than encrypting one bit at a time as in stream ciphers. For example, a common block cipher, AES, encrypts 128 bit blocks with a key of predetermined length: 128, 192, or 256 bits. Block ciphers are pseudorandom permutation (PRP) families that operate on the fixed size block of bits. PRPs are functions that cannot be differentiated from completely random permutations and thus, are considered reliable, until proven unreliable.

Block cipher modes of operation have been developed to eliminate the chance of encrypting identical blocks of text the same way, the ciphertext formed from the previous encrypted block is applied to the next block. A block of bits called an initialization vector (IV) is also used by modes of operation to ensure ciphertexts remain distinct even when the same plaintext message is encrypted a number of times.

Some of the various modes of operation for block ciphers include CBC (cipher block chaining), CFB (cipher feedback), CTR (counter), and GCM (Galois/Counter Mode), among others. Above is an example of CBC mode.

Where an IV is crossed with the initial plaintext block and the encryption algorithm is completed with a given key and the ciphertext is then outputted. This resultant cipher text is then used in place of the IV in subsequent plaintext blocks.

For information on the block ciphers that are implemented in wolfSSL or to learn more about the wolfSSL lightweight, embedded SSL library, go to wolfssl.com or contact us at facts@wolfssl.com.

References

[1] Pseudorandom permutation. (2014, November 23). In Wikipedia, The Free Encyclopedia.
Retrieved 22:06, December 18, 2014, from 
http://en.wikipedia.org/w/index.php?title=Pseudorandom_permutation&oldid=635108728.

[2] Margaret Rouse. (2014). Block Cipher [Online]. Available URL:
http://searchsecurity.techtarget.com/definition/block-cipher.

[3] Block cipher mode of operation. (2014, December 12). In Wikipedia, The Free
Encyclopedia. Retrieved 22:17, December 18, 2014, from
http://en.wikipedia.org/w/index.php?title=Block_cipher_mode_of_operation&oldid=637837298

[4] Wikimedia. (2014). Available URL:
http://upload.wikimedia.org/wikipedia/commons/d/d3/Cbc_encryption.png.

wolfSSL is proud to announce that several wolfCrypt algorithms have received FIPS 140-2 algorithm certificates. The National Institute of Standards and Technology (NIST) website has been updated to reflect wolfSSL`s validation.

wolfSSL`s wolfCrypt has received the following certificate numbers and can be viewed at the respective links.

AES validation certification #3157
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=3157

Triple DES validation certification #1800
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=1800

RSA validation certification #1602
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=1602

SHS validation certification #2614
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=2614

DRBG validation certification #650
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=650

HMAC validation certification #1990
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?validation=1990

These validations reflect wolfSSL`s commitment to provide the highest quality security standards.
The open source community and federal entities alike can now enjoy wolfSSL`s small footprint designed for embedded systems while taking advantage of the latest in security protocols.

References:
https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf

If you are looking for an SSL/TLS library to provide security in connected ARM environments, wolfSSL is by far the best choice. wolfSSL is an ARM partner, and our code has been optimized for ARM environments. Public key operations in CyaSSL (wolfSSL) have optimized assembly code that gives wolfSSL faster RSA, Diffie-Hellman, and DSA times.

Optimized assembly code for public key operations can be found in asm.c and are easy to use, simply run ./configure –enable-fastmath and for stack usage reduction we also recommend using TFM_TIMIN_RESISTANT.

For any question regarding wolfSSL in ARM environments please contact us at facts@wolfssl.com.

Below is a link to wolfSSL’s SSL/TLS tutorial video on setting up a basic client and server with the CyaSSL lightweight, embedded SSL/TLS library. This video provides a detailed step-by-step set of instructions, including code, for incorporating CyaSSL into an application. The tutorial walks through Chapter 11 of the CyaSSL manual.

SSL/TLS Tutorial with CyaSSL Lightweight SSL:
https://www.youtube.com/watch?v=-Smp3X1eWNQ

For more information please contact us at facts@wolfssl.com or go to www.wolfssl.com. Instructions for building CyaSSL may be found in Chapter 2 of the CyaSSL Manual.

Some TLS implementations are vulnerable to the October POODLE attack that at the time was thought to be limited to SSLv3 only: https://www.imperialviolet.org/2014/12/08/poodleagain.html .  These implementations are incorrectly using a SSLV3 decoding function while in TLS mode.  wolfSSL is not susceptible, it correctly uses TLS decoding while in TLS mode.  We would like to reiterate Adam Langley’s advice to use TLS 1.2 with an AEAD cipher suite whenever possible.  wolfSSL supports TLS 1.2 and has 3 cipher suite types supporting AEAD; AES-GCM, AES-CCM, and CHACHA20-POLY1305.  29 different AEAD cipher suites are available with TLS 1.2 in wolfSSL.  Please contact us at facts@wolfssl.com if you have any questions or comments.

CyaSSL version 3.3.0 offers:

• Secure countermeasures for Handshake message duplicates, CHANGE CIPHER without FINISHED, and fast forward attempts added to our source code.  Thanks to Karthikeyan Bhargavan from the Prosecco team at INRIA Paris-Rocquencourt for the report.  This is an important fix and all users should update!
• Complete testing for FIPS 140-2 version submitted to NIST.  FIPS 140-2 source code now available.
• Removes SSLv2 Client Hello processing for enhanced security, can be enabled with OLD_HELLO_ALLOWED
• Protocol level control:  User can now control TLS protocol down-cycling to a minimum downgrade version with CyaSSL_SetMinVersion().  For example, you could reject handshakes at a protocol level less than TLS 1.1.
• Small stack improvements at TLS/SSL layer, to benefit environments with limited available stack.
• TLS Master Secret generation and Key Expansion are now exposed at the API level
• Adds client side Secure Renegotiation, * not recommended, ever! *
• Client side session ticket support.  This feature is not fully tested with Secure Renegotiation, so don’t use Secure Renegotiation.
• Allows up to 4096-bit DHE at TLS Key Exchange layer
• Handles non standard SessionID sizes in Hello Messages
• PicoTCP Support added
• TLS Sniffer now supports SNI Virtual Hosts
• TLS Sniffer now handles non HTTPS protocols using STARTTLS
• TLS Sniffer can now parse records with multiple messages
• TI-RTOS updates or enhances support
• Fix for ColdFire optimized fp_digit read only in explicit 32bit case
• Added ADH Cipher Suite ADH-AES128-SHA for EAP-FAST

Stay up to date with what is happening with wolfSSL, you can follow our blog at http://www.wolfssl.com/yaSSL/Blog/Blog.html

If you have any questions please feel free to contact us anytime at facts@wolfssl.com or (425)245-8247.
We look forward to hearing from you!

Thank You!
wolfSSL

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 facts@wolfssl.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:
http://www.picotcp.com/picotcp-and-cyassl-integration

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 facts@wolfssl.com.

PicoTCP: http://www.picotcp.com/
TASS Belgium (acquired by Altran): https://www.altran.com/nl/en/