RECENT BLOG NEWS

As many people know, the OpenSSL project is struggling with FIPS, and their new FIPS release is not expected until December 2020. The version of OpenSSL that supports FIPS goes into End Of Life and is no longer supported in December of 2019.

This means that OpenSSL users will not have a supported package for over a year. This is a big issue for companies that rely on security.

To fill this breach, wolfSSL has integrated our FIPS certified crypto module with OpenSSL as an OpenSSL engine. This means that:

1. OpenSSL users can get a supported FIPS solution, with packages available up to the 24×7 level,

2. The new wolfCrypt FIPS solution also supports the TLS 1.3 algorithms, so your package can support TLS 1.3,

3. You can support hardware encryption with your package, as the new wolfCrypt solution has full hardware encryption support.

Additionally, should you be using one of the OpenSSL derivatives like BoringSSL, we can also support you.

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

We love you.

Team wolfSSL

In the latest release of wolfSSL, we have added a new port for using wolfSSL with OpenVSwitch. OpenVSwitch is a multilayer switch to provide switching for hardware virtualization environments. With wolfSSL support, users can now build OpenVSwitch with the configure option --with-wolfssl. 

The addition of OpenVSwitch is available in wolfSSL 4.2.0, which can be downloaded here. 

Changes made to OpenVSwitch for wolfSSL compatibility can be found on the OpenVSwitch GitHub. 

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

We have added in support for the open source project WebRTC (https://webrtc.org/) in wolfSSL release 4.2.0. This is a project that allows real time communication (RTC) with IoT, mobile and web browsers. Many additional API where added to the wolfSSL compatibility layer in order to plug wolfSSL into WebRTC instead of OpenSSL. Some of those additional API added are:

• SSL_CIPHER_get_id
• SSL_CIPHER_get_rfc_name
• SSL_get_cipher_by_value
• X509_print_ex
• X509_NAME_add_entry_by_NID
• X509_time_adj
• X509_time_adj_ex
• DTLSv1_get_timeout
• DTLSv1_handle_timeout
• DTLSv1_set_initial_timeout_duration
• SSL_CTX_set_current_time_cb
• PEM_write_bio_RSA_PUBKEY
• PEM_read_bio_RSA_PUBKEY
• PEM_write_bio_PUBKEY
• EVP_PKEY_missing_parameters
• EVP_PKEY_cmp
• BN_is_negative
• BIO_set_retry_write

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

The option to have a massive TITAN size session cache is now available in wolfSSL 4.2.0. This can hold over 2 million session entries and works well for use in desktops and high load environments that have many long lasting session ID’s. To turn on the new session cache size use the enable option --enable-titancache, or the macro TITAN_SESSION_CACHE if building without autoconf. This option is meant for extreme use cases where --enable-hugecache (HUGE_SESSION_CACHE) is just not enough. It works well with systems that need over 200 new sessions per second and also need to handle numerous long lasting sessions.

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

Are you a MQX user looking for SFTP client or server support?  If so, you’ll be happy to hear that wolfSSH SFTP now supports NXP/Freescale MQX 4.2!

MQX 4.2 support (using the MFS file system and RTCS TCP/IP stack) was added as part of the wolfSSH 1.4.3 release.  MQX 4.2, or “MQX Classic”, is a Real-Time Operating System (RTOS) created by NXP/Freescale and commonly used on 32-bit MCUs and MPUs from NXP.  The wolfSSH SFTP MQX 4.2 port was tested and validated on a NXP K70-based platform.  When compiling wolfSSH for NXP/Freescale MQX 4.2, the FREESCALE_MQX define should be used.

wolfSSH is a lightweight, portable SSHv2 implementation with support for both client and server functionalities.  Including features such as SFTP and SCP, and supporting both password and public key authentication, wolfSSH is the ideal solution for SSH and file transfer requirements on embedded systems.  wolfSSH is backed by the wolfCrypt cryptography library and can use features of wolfCrypt such as expansive hardware cryptography support, FIPS 140-2 validated cryptography, DO-178, and more!

wolfSSH can be downloaded from the wolfSSL download page or via GitHub, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

wolfSSL has added in many new OpenSSL compatibility API’s in the recent release, wolfSSL 4.2.0. The compatibility layer previously was impressive with upwards of 600 hundred of the most common API used, but in the effort to make transitioning projects that currently use OpenSSL, over to using wolfSSL, we added more than 198 additional API. These API additions supported many open source projects such as building with Apache (https://www.apache.org/) and WebRTC. There were also improvements done in the last release for existing API’s and enhancements to their functionality.

There are too many new API to list all, but here are some of them:

• SSL_CIPHER_get_id
• SSL_CIPHER_get_rfc_name
• SSL_get_cipher_by_value
• X509_print_ex
• X509_NAME_add_entry_by_NID
• X509_time_adj
• X509_time_adj_ex
• DTLSv1_get_timeout
• DTLSv1_handle_timeout
• DTLSv1_set_initial_timeout_duration
• SSL_CTX_set_current_time_cb
• PEM_write_bio_RSA_PUBKEY
• PEM_read_bio_RSA_PUBKEY
• PEM_write_bio_PUBKEY
• EVP_PKEY_missing_parameters
• EVP_PKEY_cmp
• BN_is_negative
• BIO_set_retry_write
• ASN1_STRING_type
• EVP_aes_128_gcm, EVP_aes_192_gcm, EVP_aes_256_gcm
• EVP_CIPHER_CTX_ctrl
• EVP_PKEY_sign
• EVP_PKEY_sign_init
• RSA_print
• RSA_NO_PADDING
• RSA_PKCS1_PSS_PADDING
• wolfSSL_EVP_CIPHER_CTX_set_iv_length
• GENERAL_NAMES_free
• i2a_ASN1_OBJECT
• PKCS5_PBKDF2_HMAC
• X509_get_ext_by_NID
• X509V3_EXT_print
• ASN1_STRING_print
• GENERAL_NAME_free
• …. (and more)

If you have a FIPS project in jeopardy with the upcoming lapse in OpenSSL support, an easy fix is to plug in wolfSSL. If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

wolfSSH v1.4.3 has been released. This version of wolfSSH includes several fixes and new features. The primary new feature is a wolfSFTP port to MQX 4.2. Please see the change log for more details. Included are some portability fixes between versions of C compilers, a clean up of some obvious issues with the examples, and improved interoperability with PuTTY.

You can download this latest release from the wolfSSL download portal. Additional information wolfSSH can be found on the wolfSSH product page. If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247. Be sure to stay up to date with our GitHub repository. Please give us a star!

wolfSSH v1.4.3 (10/31/2019)

1. wolfSFTP port to MQX 4.2 (MQX/MFS/RTCS)
2. Maintenance and bug fixes
3. Improvements and additions to the test cases
4. Fix some portability between C compilers
5. Fixed an issue in the echoserver example where it would error sometimes on shutdown
6. Improvement to the global request processing
7. Fixed bug in the new keys message handler where it reported the wrong size in the data buffer; invalid value was logged, not used
8. Fixed bug in AES initialization that depended on build settings
9. Improved interoperability with puTTY
10. Added user auth callback error code for too many password failures
11. Improvements to the Nucleus filesystem abstraction
12. Added example for an “autopilot” file get and file put with the wolfSFTP example client

As many people know, the OpenSSL project is struggling with FIPS, and their new FIPS release is not expected until December 2020. The version of OpenSSL that supports FIPS goes into End Of Life and is no longer supported in December of 2019.

This means that OpenSSL users will not have a supported package for over a year. This is a big issue for companies that rely on security.

To fill this breach, wolfSSL has integrated our FIPS certified crypto module with OpenSSL as an OpenSSL engine. This means that:

1. OpenSSL users can get a supported FIPS solution, with packages available up to the 24×7 level,

2. The new wolfCrypt FIPS solution also supports the TLS 1.3 algorithms, so your package can support TLS 1.3,

3. You can support hardware encryption with your package, as the new wolfCrypt solution has full hardware encryption support.

Additionally, should you be using one of the OpenSSL derivatives like BoringSSL, we can also support you.

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

We love you.

Team wolfSSL

Saficard is a French company specializing in solutions for healthcare payment management. One of their products is a Point-of-Sale (POS) terminal designed to accept the Vitale Card. The Vitale Card is a French health insurance card that stores social security information and allows patients to be reimbursed for healthcare costs. The card works with various smart card standards, such as: EMV, IAS-ECC, and ISO (joinup).

The French government has created strict security standards for processing healthcare bills using the Vitale Card. Among these standards are using Cryptography Message Syntax (PKCS#7) and TLS for transmitting healthcare transactions.

Saficard faced problems finding a lightweight-portable cryptography library written in C for their Point-of-Sale terminals. Their solution was using wolfSSL + wolfCrypt to implement PKCS#7 and TLS on the iWL250 terminal by Ingenico.

Read more about the Saficard Case Study and check out Saficard.
Vitale Card Information at joinup

If you have any questions about using wolfSSL products for your project, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

The NXP Memory-Mapped Cryptographic Acceleration Unit (mmCAU) is on many Kinetis and ColdFire microcontrollers. It improves symmetric AES and SHA performance as compared to our software based implementation. The v4.2.0 enhanced the MMCAU support to use multiple blocks against hardware and optimizes to avoid memory copies (memcpy) when able. This resulted in a 20-78% improvement.

Features:

• Enhancement for NXP MMCAU to process more than one block at a time.
• Added optional buffer alignment detection macro WC_HASH_DATA_ALIGNMENT to avoid memcpy.
• Added MD5 and SHA-1 support for XTRANSFORM_LEN to process blocks.
• Cleanups for consistency between algorithms and code commenting.

Improved MMCAU performance: SHA-1 by 35%, SHA-256 by 20% and MD5 by 78%.

NXP K64 MMCAU with wolfSSL v4.2.0:

MD5                  8 MB took 1.000 seconds,    7.910 MB/s

SHA                  4 MB took 1.005 seconds,    3.644 MB/s

SHA-256              2 MB took 1.006 seconds,    2.306 MB/s

NXP K64 MMCAU with wolfSSL v4.1.0:

MD5                  4 MB took 1.004 seconds,    4.450 MB/s

SHA                  3 MB took 1.006 seconds,    2.670 MB/s

SHA-256              2 MB took 1.008 seconds,    1.913 MB/s

Changes are in GitHub pull request #2481 and in the wolfSSL v4.2.0 release.

If you have any questions or run into any issues, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.