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. wolfSSL also has a support-specific blog page dedicated to answering some of the more commonly received support questions.

Additional OpenSSL Compatibility API

With each release of the wolfSSL embedded SSL/TLS library, new improvements and feature additions are always included. The wolfSSL team has made sure to improve and update support for various open source projects. This holiday release of wolfSSL 4.3.0, we are happy to include expansions in our OpenSSL Compatibility layer. 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. As a result we are constantly expanding the OpenSSL compatibility API to help people migrate from OpenSSL to wolfSSL. In this release the API wolfSSL_CertManagerGetCerts() and wolfSSL_X509_STORE_GetCerts() were added for retrieving certificates.

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

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.

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

Added new support for MQX v5

With each release of the wolfSSL embedded SSL/TLS library, new improvements and feature additions are always included. The wolfSSL team has made sure to incrementally improve and update support for our various partners. In our wolfSSL 4.3.0 holiday release, we are happy to bring improved support for MQX. wolfSSL has added new FREESCALE_MQX_5_0 macro for MQX v5 support!

For those who are unaware MQX v5 is a continuation of the MQX Classic product available under low-cost commercial licensing terms. MQX v4.2 is no longer available and has been superseded by v5. MQX v5 is backward compatible with MQX Classic and includes a multitasking RTOS kernel, a TCP/IP stack (RTCS) with Internet protocol v6 (IPv6), embedded MS-DOS file system (MFS), USB host/device stack and task-aware debugging. MQX v5 board support packages (BSPs) are available for a number of platforms, with other BSPs available upon request.

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

Support for Single Precision 4096-bit RSA/DH Operations

With the holiday release of wolfSSL 4.3.0, we have continued to optimize wolfSSL’s math library performance by expanding our single precision math operations. This greatly speeds up some set key sizes with RSA, ECC, and DH operations. In this release support for 4096-bit RSA/DH operations was added!

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

Poly1305 AVX2 Assembly Optimization Fix

With each release of the wolfSSL embedded SSL/TLS library, new improvements and feature additions are always included. In the new release of wolfSSL 4.3.0, we are happy to have improved hardware cryptography support including a Poly1305 AVX2 assembly optimization fix for carry with large input values.

ChaCha20-Poly1305 is a relatively new authenticated encryption algorithm. It was designed as an alternative to AES-GCM. The algorithm is simple and fast on CPUs that do not have hardware acceleration for AES and GCM.

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

wolfSSL Support with Qt5 (#Qt5)

Calling all developers of Qt! wolfSSL is continuously adding new features and support for various open source projects. One of the most recent projects wolfSSL has been working on is support for Qt. We are excited to announce wolfSSL support with Qt version 5.12 and 5.13.

The recent wolfSSL integration with Qt provides a lightweight and performance-minded alternative for the Qt Network backend SSL/TLS. The QSslSocket class makes it easy to add encryption to your application. Now, wolfSSL makes it secure!

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

To view more open source projects wolfSSL has teamed up with, visit https://www.wolfssl.com/community/.
To learn more about the advantages of using wolfSSL, visit our page on “wolfSSL vs. OpenSSL”.

wolfSSL MQTT Sensor Network (MQTT-SN)

The MQTT Sensor Network standard provides a lightweight networking protocol perfectly suited for low cost, low power hardware. The protocol allows using small topic identifiers in place of the full topic name when sending and receiving publish data.

The wolfMQTT SN Client implementation is based on the OASIS MQTT-SN v1.2 specification. The SN API is configured with the –enable-sn option. There is a separate API for the sensor network API, which all begin with the “SN_” prefix. The wolfMQTT SN Client operates over UDP, which is distinct from the wolfMQTT clients that use TCP. The following features are supported by the wolfMQTT SN Client:

  • Register
  • Will topic and message set up
  • Will topic and message update
  • All QoS levels
  • Variable-sized packet length field

You can download the latest release of wolfMQTT from our website or clone the repository from 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.

wolfSSL + Apache httpd

In the latest wolfSSL releases, we have added 200+ new API to our OpenSSL compatibility layer. Many of these new API were added for providing support for Apache HTTP Server. We are excited to announce that as of version 4.2.0, wolfSSL now provides support for the Apache web server with the enable option --enable-apachehttpd. This means you can now build Apache with the latest, most robust security provided by the wolfSSL SSL/TLS and wolfCrypt libraries.

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

For comparison between wolfSSL and OpenSSL, visit https://www.wolfssl.com/docs/wolfssl-openssl/.

wolfSSL Examples Repository

From the early days of the wolfSSL library, we have provided example clients and servers with wolfSSL. These examples have showed how easy it is to use wolfSSL in various configurations. We also use them to help test the library. Over the years we’ve added new features available with TLS to our examples, and our examples have grown a little complicated.

Enter the wolfSSL Examples GitHub repository. We tasked some of our interns, with little to no experience with the wolfSSL library, to write some example clients and servers that set up and test various types of connections. They give you a bare-bones simple demonstration on how to set up a client or server using wolfSSL. We also have examples showing off how to use some features of the library like the certificate manager. Check them out!

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

wolfSSL and Application Binary Compatibility

To help out with customers who want to update the wolfSSL library without needing to change their application, wolfSSL Inc is striving to maintain application binary compatibility with a subset of our API. As of wolfSSL v4.3.0, the following functions will be compatible across all releases of wolfSSL moving forward:

wolfSSL_acceptwolfSSL_check_domain_name
wolfSSL_CleanupwolfSSL_connect
wolfSSL_CTX_freewolfSSL_CTX_GetDevId
wolfSSL_CTX_load_verify_locationswolfSSL_CTX_new
wolfSSL_CTX_SetDevIdwolfSSL_CTX_SetEccSignCb
wolfSSL_CTX_SetMinVersionwolfSSL_CTX_set_session_cache_mode
wolfSSL_CTX_set_timeout wolfSSL_CTX_set_verify
wolfSSL_CTX_use_certificate_chain_filewolfSSL_CTX_use_certificate_file
wolfSSL_CTX_use_PrivateKey_filewolfSSL_CTX_UseSNI
wolfSSL_flush_sessionswolfSSL_free
wolfSSL_get_errorwolfSSL_get_peer_certificate
wolfSSL_GetRNGwolfSSL_get_session
wolfSSL_get_sessionID wolfSSL_Init
wolfSSL_newwolfSSL_pending
wolfSSL_readwolfSSL_SetDevId
wolfSSL_set_fdwolfSSL_set_session
wolfSSL_set_timeoutwolfSSL_shutdown
wolfSSL_UseALPNwolfSSL_UseSNI
wolfSSL_use_certificate_chain_filewolfSSL_use_certificate_file
wolfSSL_use_PrivateKey_filewolfSSL_write
wolfSSL_X509_freewolfSSL_X509_get_next_altname
wolfSSL_X509_get_issuer_namewolfSSL_X509_get_subject_name
wolfSSL_X509_load_certificate_filewolfSSL_X509_NAME_oneline
wolfSSL_X509_notAfterwolfSSL_X509_notBefore
wolfTLSv1_2_client_methodwolfTLSv1_2_server_method
wolfTLSv1_3_client_methodwolfTLSv1_3_server_method
wolfCrypt_InitwolfCrypt_Cleanup
wc_ecc_free wc_ecc_import_x963
wc_ecc_init_exwc_ecc_key_free
wc_ecc_key_newwc_ecc_make_key_ex
wc_RNG_GenerateBlockwc_rng_new
wc_ecc_sign_hashwc_rng_free
wc_InitRng
wc_ecc_make_key
wc_ecc_check_key
wc_ecc_init
wc_ecc_fp_free
wc_ecc_shared_secret
wc_ecc_size
wc_ecc_sig_size_calc
wc_ecc_sig_size
wc_ecc_ctx_new
wc_ecc_ctx_free
wc_ecc_ctx_reset
wc_ecc_encrypt
wc_ecc_decrypt
wc_ecc_sign_hash
wc_ecc_verify_hash
wc_InitCert
wc_MakeSelfCert
wc_MakeCert
wc_SignCert
wc_MakeCertReq
wc_SetIssuer
wc_SetSubject
wc_SetSubjectRaw
wc_GetSubjectRaw
wc_SetAltNames
wc_SetIssuerBuffer
wc_SetIssuerRaw
wc_SetSubjectBuffer
wc_SetAltNamesBuffer
wc_SetDatesBuffer
wc_SetCert_Free
wc_DerToPem
wc_EccKeyToDer
wc_EccPrivateKeyDecode
wc_EccPublicKeyDecode
wc_EccPublicKeyToDer
wc_ecc_export_x963
wc_ecc_export_x963_ex
wc_ecc_import_private_key
wc_ecc_rs_to_sig
wc_ecc_import_raw
wc_ecc_export_private_only
wc_GetErrorString
wc_ChaCha20Poly1305_Decrypt
wc_ChaCha20Poly1305_Encrypt
wc_CertNewwc_CertFree

We have added some testing to our already extensive testing plan to verify these functions do not change.

Given that the security landscape is an always changing surface, we want to make sure you are able to upgrade wolfSSL as easily as possible. There will always be some new attack on the protocol or a cipher and keeping wolfSSL up to date in your product is important to us, and for everyone.

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

Posts navigation

1 2 3 91 92 93 94 95 96 97 187 188 189

Weekly updates

Archives