Category: Uncategorized

wolfSSL now provides support for complete RTCA DO-178C level A certification! wolfSSL will offer DO-178 wolfCrypt as a commercial off -the-shelf (COTS) solution for connected avionics applications. Adherence to DO-178C level A will be supported through the first wolfCrypt COTS DO-178C certification kit release that includes traceable artifacts for the following encryption algorithms:

• SHA-256 for message digest
• AES for encryption and decryption
• RSA to sign and verify a message.
• Chacha20_poly1305 for authenticated encryption and decryption.

The primary goal of this initial release is to provide the proper cryptographic underpinnings for secure boot and secure firmware update in commercial and military avionics. wolfSSL brings trusted, military-grade security to connected commercial and military aircraft. Avionics developers now have a flexible, compact, economical, high-performance COTS solution for quickly delivering FIPS 140-2 validated crypto algorithms can be used in DO-178 mode for combined FIPS 140-2/DO-178 consumption. The wolfCrypt cryptography library FIPS 140-2 validation certificates can be applied to DO-178 uses. 

Optimization Support

We understand that securely rebooting avionic systems has rigorous performance requirements. As such, we’re here to help with cryptographic performance optimizations through our services organization. 

To download and view the most recent version of wolfSSL, the wolfSSL GitHub repository can be cloned from here: https://github.com/wolfssl/wolfssl.git, and the most recent stable release can be downloaded from the wolfSSL download page here: https://www.wolfssl.com/download/.

wolfSSL DO-178 product page: https://www.wolfssl.com/wolfssl-support-178-dal/.

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

As many people know, cURL is very popular in automotive systems.  cURL is used in infotainment, ADAS, entry and control systems.

Because many cURL users in automotive are interested in conforming to the MISRA C standard, wolfSSL is developing a version of cURL that conforms to MISRA and consumes our MISRA conformant cryptography.

If you are interested in a MISRA based cURL implementation, built under ASPICE, contact us at facts@wolfssl.com, or call us at +1 425 245 8247.

We love you.

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 BoringSSL.

Below lists some of the additional API added to the wolfSSL compatibility layer for WebRTC support:

• 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

Notable advantages of choosing to build WebRTC with wolfSSL are evident through wolfSSL’s superior security implementations, including support for FIPS, PKCS#11, hardware encryption, TLSv1.3, and more. Additionally, 24×7 support and consulting services are available to help build your wolfSSL + WebRTC project.

The pull request with the latest updates for WebRTC can be found here: https://github.com/wolfSSL/wolfssl/pull/2585.
Upstream changes for WebRTC that include wolfSSL support can be found here: https://webrtc-review.googlesource.com/c/src/+/159760.

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 wolfSSL embedded SSL/TLS library provides support for various open source projects, including Nginx. For those who are unfamiliar, Nginx is a high-performance, high-concurrency web server. Like wolfSSL, it is also compact, fast, and highly scalable. Additionally, wolfSSL also provides support for TLS 1.3 and features such as OCSP, so Nginx servers can be configured with the latest and most secure protocols.

Nginx and wolfSSL make a likely pairing because they are both lean, compact, fast, and scale well under high volumes of connections. wolfSSL + Nginx is available in a public GitHub repository.  The configure option --enable-nginx will compile the wolfSSL libraries with Nginx support.

wolfSSL also provides FIPS and FIPS ready versions of the wolfCrypt library, meaning Nginx can be built FIPS compliant. More information on wolfCrypt FIPS can be found on the wolfCrypt FIPS FAQ 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.

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.