RECENT BLOG NEWS

So, what’s new at wolfSSL? Take a look below to check out the most recent news.
Or sign up to receive weekly email notifications containing the latest news from wolfSSL.
In addition, wolfSSL now has a support-specific blog page dedicated to answering some of the more commonly received support questions.

wolfSSL Support for WebRTC

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.

For questions about the use of wolfSSL with WebRTC, 24×7 support, or for any additional questions contact us at facts@wolfssl.com.

wolfSSL + Nginx

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.

For more information on wolfSSL + Nginx, TLS 1.3, OCSP, FIPS, or for any additional questions, contact facts@wolfssl.com.

wolfCrypt as an engine for OpenSSL

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.

Contact us at facts@wolfssl.com if you would like to learn more!

We love you.

Team wolfSSL

wolfSSL with OpenVSwitch

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

For more information about the compatibility layer, building with OpenVSwitch, or any additional questions, contact us at facts@wolfssl.com.

wolfSSL Support for WebRTC

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

For questions about the use of wolfSSL with WebRTC contact us at facts@wolfssl.com.

wolfSSL New TITAN Cache Option

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.

For more information about the TITAN cache build contact us at facts@wolfssl.com.

wolfSSH SFTP Support for MQX 4.2

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.  Please contact facts@wolfssl.com with any questions or inquiries.

wolfSSL 4.2.0 Compatibility Layer Expansion

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. Let us know if your project needs any API that we are missing by contacting us at facts@wolfssl.com.

wolfSSH v1.4.3 Now Available!

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. For more information on platform support or for questions regarding wolfSSH, contact us at facts@wolfssl.com. 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

wolfCrypt as an engine for OpenSSL

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.

Contact us at facts@wolfssl.com if you would like to learn more!

We love you.

Team wolfSSL

Posts navigation

1 2 3 4 5 103 104 105

Weekly updates

Archives

Latest Tweets