RECENT BLOG NEWS

Today we’d like to give a quick shout out to Igor Barshteyn! He is a long time and active member of the cryptography and information security communities. His interests are very apparent in his posts on LinkedIn.

Besides sleuthing out the the NIST post-quantum draft standards the day before their release and a multitude of other interesting posts, he has come up with a script to allow for easy experimentation in wolfSSL with post-quantum algorithms hybridized with NIST ECC curves in our fips-ready releases. But why would he do that?

Well, if you’re interested in cryptographic compliance, then you will know that the NSA’s CNSA 2.0 guidance requires the use of Kyber. You’ll also know that FIPS 140-2/3 requires the use of FIPS approved ECC curves for key exchange. Moreover, NIST has stated that an ECC key exchange done in a FIPS 140 approved mode of operation can be hybridized a with a post-quantum algorithm and still be considered in a FIPS 140 approved mode of operation. See FQAs for more detail.

Are you curious to see how hybrid FIPS 140 approved mode of key exchange hybridized with the CNSA 2.0 approved Kyber will perform in your environment or on your system? You can find out today!! Check out Igor’s post which has great instructions and a link to his script!Are you curious to see how hybrid FIPS 140 approved mode of key exchange hybridized with the CNSA 2.0 approved Kyber will perform in your environment or on your system? You can find out today!! Check out Igor’s post which has great instructions and a link to his script!

If you have questions on any of above, please contact us at facts@wolfSSL.com, or call us as +1 425 245 8247.

Download wolfSSL

Are you seeking a superior alternative to OpenSSL with better support and smoother workflow?
wolfSSL can fulfill your needs, addressing the gaps you might be experiencing while using OpenSSL. Join our upcoming webinar hosted by wolfSSL engineer Anthony, where he will focus on advantages of switching to wolfSSL. Discover why choosing wolfSSL over OpenSSL can reshape your projects.

Watch the webinar here: Migrate from OpenSSL to wolfSSL

Sneak peek of the webinar:

• Certified FIPS provider
• Support for the QUIC protocol (–enable-quic)
• Support for Post-quantum integration
• Top-notch support services
• And much more!

Anthony will provide in-depth insights into what sets wolfSSL apart from OpenSSL. Watch it now to explore the potential benefits of using wolfSSL. Let us introduce you to solutions that work best for your projects!

As always, our webinars will include Q&A sessions throughout the webinar. If you have questions on any of the above, please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247.

Download wolfSSL

We added a benchmark running on Raspberry Pi PIco-W. It runs with Cortex M0+, 125MHz. If you are interested in how wolfSSL/wolfCrypt works on low end MCU, this should be a good example benchmark to look into.

Here are some highlights:

• Hash operations such as SHA256 run faster than 1 M bytes per second.
• Symmetric algorithms like AES-GCM enc/dec faster than 300 k bytes per second.
• ECDH keygen/agreement, ECDSA sign/verify around 100mSec to 50mSec per operation.

Visit our ‘Raspberry Pi Pico-W’ benchmark page for further details.

If you have questions on any of the above, please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247.
Download wolfSSL

wolfSSL is delighted to announce that we have added a secure way for sensors to communicate to the gateway using DTLS and MQTT-SN! We used the Paho MQTT-SN Gateway project’s recent addition of DTLS support for testing.

Testing details are in the pull request.

Let us know what you think by sending a note to facts@wolfSSL.com.

You can download the latest release, or clone directly from our GitHub repository.
While you’re there, show us some love and give the wolfMQTT project a Star!

If you have questions on any of the above, please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247.

Download wolfSSL

Join the webinar to discover how the latest SM cipher implementations from wolfSSL comply with Chinese regulations and can secure your critical systems! wolfSSL engineer Sean will reveal all the details to help you find the best solutions for your critical systems on September 7th at 2pm PT.

Watch the webinar here: SM ciphers are implemented in wolfSSL

The Chinese government mandates the use of SM2, SM3, and SM4 in critical systems such as automobiles, avionics and more. wolfSSL is proud to announce our supported versions of these ciphers tailored to our customers in the Chinese market. We also have a plan to release the ZUC stream cipher later this year to completely satisfy SM9. Additionally, we’re actively communicating with labs regarding support of OSCCA certification in the future.

This exciting development is fantastic news for our customers in the Chinese market, ensuring they remain compliant with the latest regulations.

Benefits of using wolfSSL products:

1. The SM Ciphers are fully supported in wolfSSL’s TLS 1.3 and DTLS 1.3 implementations.
2. wolfSSH, wolfBoot and our other products will support ShangMi ciphers.
3. ARM, Intel, and RiscV assembly is in the works for our SM implementations for maximum performance
4. We support bare metal for SM2, SM3, and SM4
5. We have maximized performance and minimized size, so the ShangMi algorithms will work well for embedded systems use cases on a wide variety of microcontrollers (MCU’s). They will be available for all of the MCU silicon that we currently support, including STM32, NXP i.MX, RISC-V, Renesas RA, RX, and Synergy, Nordic NRF32, Microchip PIC32, Infineon Aurix, TI MSP, and many others
6. Our GPLv2 versions of the SM ciphers are available on GitHub

Commercially licensed versions are available.

Don’t miss this opportunity to discover solutions for your system security and compliance. Join our webinar to explore the full potential of SM cipher implementations from wolfSSL.

Watch it now!

As always, our webinars will include Q&A sessions throughout the webinar. If you have questions on any of the above, please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247.

Download wolfSSL

At wolfSSL we support hardware cryptography for a wide range of platforms. The benefits of hardware cryptography include reduced code footprint size, improved security, acceleration of cryptographic operations, and utilization of true random number generators. For example, this allows everything from wolfBoot to TLS cipher suites to enjoy acceleration of cryptographic operations.

Furthermore, we have deep partnerships with industry leaders such as Intel, NXP, and Renesas. We support standard Intel instruction extensions such as AES-NI, AVX, and ADX and BMI2, and have recently published a joint whitepaper on using wolfBoot with 11th Gen Intel Core processors. We also support NXP’s Cryptographic Accelerator and Assurance Module (CAAM), and have leveraged this for hardware acceleration on a number of NXP i.MX series processors. Other examples include Espressif and Analog Devices, to name but a few.

If you’re curious for a list of every hardware cryptography scheme and platform we have enabled, then read on:

• • AES-NI: Intel 64 and IA-32 Xeon and Core, and AMD Zen processor families. 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    AES–ECB	128, 192, 256 bit
    AES–CTR	128, 192, 256 bit

    References:

    1. https://www.wolfssl.com/white-paper-applying-wolfboot-to-11th-gen-intel-core-processors-for-secure-boot/

• • AVX1/AVX2: Intel and AMD x86. 
    

    SHA3, SHA2	SHA-256, SHA-384, SHA-512
    AES–GCM	128, 192, 256 bits
    ChaCha20-Poly1305	256 bit AEAD stream cipher
    Poly1305

    References:

    1. https://www.wolfssl.com/wolfssl-performance-intel-x86_64-part-2/
    2. https://www.wolfssl.com/wolfssl-performance-intel-x86_64-part-3/
    3. https://www.wolfssl.com/intels-extended-instructions-accelerates-hash-algorithms/

• • Intel ADX and BMI2: Intel and AMD x86. 
    

    RSA
    Curve25519	256 bit
    Ed25519	256 bit

    References:

    1. https://www.wolfssl.com/wolfssl-performance-intel-x86_64-part-5/
    2. https://www.wolfssl.com/wolfssl-performance-intel-x86_64-part-6/

• • RDRAND/RDSEED: Intel 64 and IA-32, and AMD Zen processor families. 
    

    RNG

    References:

    1. https://www.intel.com/content/www/us/en/developer/articles/guide/intel-digital-random-number-generator-drng-software-implementation-guide.html
    2. https://www.amd.com/content/dam/amd/en/documents/pdfs/developer/aocl/amd-secure-random-number-generator-library-2.0-whitepaper.pdf

• • NXP Coldfire SEC: (MCF547X and MCF548X family of processors) 
    

    AES–CBC	128, 192, 256 bit
    3DES–CBC	192 bit
    DES–CBC	64 bit

    References:

    1. https://www.wolfssl.com/docs/nxp/

• • NXP Coldfire CAU/mmCAU: (NXP Coldfire and Kinetis) 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    AES–ECB	128, 192, 256 bit
    AES–CTR	128, 192, 256 bit
    3DES
    SHA2	SHA-256
    SHA1
    HMAC	SHA1, SHA2
    MD5

    References:

    1. https://www.wolfssl.com/docs/nxp/
    2. https://www.wolfssl.com/improved-nxp-mmcau-crypto-hardware-performance/
    3. https://www.wolfssl.com/improved-nxp-mmcau-crypto-hardware-performance-2/

• • STMicroeletronics STM32 L4, F1, F2, F4 and F7: 
    

    AES–GCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    AES–ECB	128, 192, 256 bit
    AES–CTR	128, 192, 256 bit
    SHA2	SHA-224, SHA-256
    SHA1
    MD5
    RNG

    References:

    1. https://www.wolfssl.com/docs/benchmarks/#stm32
    2. https://www.wolfssl.com/docs/benchmarks/#stm32f777ni

• • Marvell (Cavium) Nitrox V and III: 
    

    AES–GCM	128 bit
    AES–CBC	128, 192, 256 bit
    RSA	2048 bit
    ECC
    ECDSA
    RNG

    References:

    1. https://www.wolfssl.com/wolfssl-asynchronous-support/
    2. https://www.wolfssl.com/wordpress/wp-content/uploads/2018/04/wolfssl_async.pdf

• • Microchip PIC32 MX/MZ: 
    

    AES–CTR	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    DES/3DES–CBC	64 bit / 192 bit
    SHA2	SHA-256
    SHA1
    HMAC	SHA1, SHA2
    MD5

    References:

    1. https://www.wolfssl.com/docs/pic32/

• • Texas Instruments Crypto Connected Launchpad: (TI TM4C series boards) 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    AES–ECB	128, 192, 256 bit
    AES–CTR	128, 192, 256 bit
    DES–CBC	64 bit
    3DES–CBC	192 bit
    SHA2	SHA-224, SHA-256
    SHA1
    MD5

    References:

    1. https://www.ti.com/lit/ug/spmu372a/spmu372a.pdf
    2. https://www.ti.com/tool/EK-TM4C129EXL

• • Nordic NRF5x: 
    

    AES–ECB	128 bit
    RNG

    References:

    1. https://www.wolfssl.com/true-random-vs-pseudorandom-number-generation/
    2. https://www.wolfssl.com/wolfssl-on-nordic-nrf52/

• • 
    Microchip/Atmel ATECC508A/ATECC608A: 

    ECC	256 bit (NIST-P256)

    References:

    1. https://www.wolfssl.com/docs/atmel/
    2. https://www.wolfssl.com/wolfssl-support-atecc508aatecc608a-crypto-coprocessor-2/
    3. https://www.wolfssl.com/using-wolfssl-on-the-atmel-atecc508a-with-tls-1-3-tls13/

• • Espressif ESP32: 
    

    AES–GCM	128, 192, 256 bits
    AES–CBC	128, 192, 256 bits
    RSA	2048
    SHA2	SHA-256, SHA-384, SHA-512

    References:

    1. https://www.wolfssl.com/docs/espressif/

• • ARMV8: 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    SHA256

    References:

    1. https://www.wolfssl.com/wolfssl-on-armv8-lemaker-2/

• • Intel QuickAssist Technology: 
    

    RSA	2048 bits
    AES–GCM	128, 192, 256 bits
    AES–CBC	128, 192, 256 bits
    3DES
    SHA2	SHA-256, SHA-384, SHA-512
    SHA1
    HMAC	SHA1, SHA2
    MD5

    References:

    1. https://www.wolfssl.com/wolfssl-asynchronous-intel-quickassist-support/

• • NXP LTC (KSDK): 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    AES–ECB	128, 192, 256 bit
    AES–CTR	128, 192, 256 bit
    DES/3DES
    ECC	256 bit
    ECDSA	256 bit
    Curve25519	256 bit
    Ed25519	256 bit
    SHA2	SHA-256, SHA-384, SHA-512
    SHA1
    HMAC	SHA1, SHA2
    MD5

    References:

    1. https://www.wolfssl.com/docs/nxp/
    2. https://www.wolfssl.com/nxp-kinetis-k8x-ltc-support-for-pki-rsaecc-with-tls13/

• • NXP SE050: 
    

    ECC	256 bit
    ECDSA	256 bit
    Curve25519	256 bit
    Ed25519	256 bit
    RNG

    References:

    1. https://www.wolfssl.com/ssltls-support-nxp-se050-wolfssl/
    2. https://www.wolfssl.com/wolfssl-nxp-se050-support-update/
    3. https://www.wolfssl.com/wolfssl-support-nxp-se050-scp03/
    4. https://www.wolfssl.com/wolfssl-nxp-se050-support-benchmarks/

• • CAAM: NXP i.MX6, i.MX7, and i.MX 8 
    

    AES–GCM	128, 192, 256 bits
    AES–CCM	128, 192, 256 bits
    AES–CTR	128, 192, 256 bits
    AES–XTS	128, 192, 256 bits
    ECC
    Curve25519	256 bit
    SHA2	SHA-256, SHA-384, SHA-512
    SHA1
    HMAC	SHA1, SHA2

    References:

    1. https://www.wolfssl.com/caam-supported-wolfssl/
    2. https://www.wolfssl.com/docs/benchmarks/#nxp_i.mx6
    3. https://www.wolfssl.com/mx6-caam-integrity-os/
    4. https://www.wolfssl.com/caamqnxi-mx8/

• • STMicroeletronics STM32 Public Key Accelerator (on WB55, H7): 
    

    AES–CBC	128, 192, 256 bit
    SHA2	SHA-224, SHA-256
    ECC	256 bit (NIST-P256)
    RNG

    References:

    1. https://www.wolfssl.com/support-stm32_pka-accelerator/

• • Silicon Labs EFR32: 
    

    AES–GCM	128, 192, 256 bit
    AES–CCM	128, 192, 256 bit
    AES–CBC	128, 192, 256 bit
    SHA2	SHA-224, SHA-256
    SHA1
    ECC	256 bit
    ECDSA	256 bit
    RNG

    References:

    1. https://www.wolfssl.com/wolfssl-adds-silicon-labs-hardware-acceleration-support/

• • Renesas RX65N and RX72N: 
    

    AES–GCM	128, 256 bit
    AES–CBC	128, 256 bit
    SHA2	SHA-256, SHA-512
    SHA1
    HMAC	SHA1, SHA2
    RNG

    References:

    1. https://www.wolfssl.com/docs/renesas/
    2. https://www.wolfssl.com/docs/wolfssl-renesas-tsip/
    3. https://www.wolfssl.com/support-renesas-tsip-v1-13-rx72n/
    4. https://www.wolfssl.com/docs/benchmarks/#renesasrx65n

• • Renesas Synergy DK-S7G2 
    

    RSA	2048 bits
    AES–CBC	128 bit
    SHA2	SHA-256
    SHA1
    HMAC	SHA1, SHA2
    ECC	256 bit
    ECDSA	256 bit

    References:

    1. https://www.wolfssl.com/docs/benchmarks/#renesasrx71m

• • Cypress PSoC6 (32-bit Arm Cortex M4) 
    

    SHA2	SHA-256, SHA-512
    ECC	Supports up to NIST P-521

• • Xilinx Versal: 
    

    AES–GCM	256 bit
    RSA	2048 bit
    ECC	NIST P-384, P-521
    SHA3	SHA-384
    RNG

    References:

    1. https://www.wolfssl.com/versal-support/

• • Xilinx Zynq UltraScale+ MPSoC 
    

    AES–GCM	256 bit
    RSA	2048, 4096 bits
    SHA3	SHA-384

    References:

    1. https://www.wolfssl.com/wolfssl-running-xilinx-versal-hardware-encryption/
    2. https://docs.xilinx.com/v/u/en-US/wp512-accel-crypto

• MAXQ1065 and MAXQ1080: 
  

  AES–GCM	128, 192, 256 bit
  AES–CCM	128, 192, 256 bit
  ECC	NIST-P256
  SHA2	SHA-256

  References:

  1. https://www.wolfssl.com/support-maxq1065-wolfssl/

Do you have a platform requiring hardware cryptographic support that isn’t on our list, or are you curious about benchmarking? Please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247 with the details of your platform and we will be glad to help you! Also, check out our wolfSSL and wolfCrypt benchmark page.

Download wolfSSL

More and more customers are asking about the Espressif ESP32 RISC-V SoC products. The answer is an enthusiastic YES. We support all of the Espressif ESP-32 chipsets, including the ESP32-C6 and the ESP32-C3 RISC-V devices.

Check out our recent video: Getting Started with wolfSSL on the ESP32. Our Espressif examples make it easier than ever to take wolfSSL for a test drive. See also the recent blog on the ESP Component Registry and other blogs on the ESP32 topic.

Shown below is an out-of-the-box, default-settings version of wolfSSL running the Benchmark app on the ESP32-C3 in a typical ESP-IDF v5.1 environment. Keep in mind there are numerous wolfSSL settings to fine-tune our libraries to your product.

We currently have RISC-V hardware acceleration in development. This means that some of the performance metrics should improve by upwards of 10x faster.

Interested in other boards as well? Check out our partial and growing list of supported boards.

I (31) boot: chip revision: v0.4
I (35) boot.esp32c3: SPI Speed      : 80MHz
I (40) boot.esp32c3: SPI Mode       : DIO
I (44) boot.esp32c3: SPI Flash Size : 2MB
------------------------------------------------------------------------------
 wolfSSL version 5.6.3
------------------------------------------------------------------------------
Math:   Multi-Precision: Wolf(SP) word-size=32 bits=3072 sp_int.c
wolfCrypt Benchmark (block bytes 1024, min 1.0 sec each)
RNG                        725 KiB took 1.027 seconds,  705.940 KiB/s Cycles per byte =  55.33
AES-128-CBC-enc             50 KiB took 1.082 seconds,   46.211 KiB/s Cycles per byte = 845.33
AES-128-CBC-dec             50 KiB took 1.088 seconds,   45.956 KiB/s Cycles per byte = 850.03
AES-192-CBC-enc             50 KiB took 1.297 seconds,   38.551 KiB/s Cycles per byte = 1013.13
AES-192-CBC-dec             50 KiB took 1.303 seconds,   38.373 KiB/s Cycles per byte = 1017.77
AES-256-CBC-enc             50 KiB took 1.511 seconds,   33.091 KiB/s Cycles per byte = 1180.73
AES-256-CBC-dec             50 KiB took 1.517 seconds,   32.960 KiB/s Cycles per byte = 1185.42
AES-128-GCM-enc             50 KiB took 1.187 seconds,   42.123 KiB/s Cycles per byte = 927.09
AES-128-GCM-dec             50 KiB took 1.186 seconds,   42.159 KiB/s Cycles per byte = 927.11
AES-192-GCM-enc             50 KiB took 1.405 seconds,   35.587 KiB/s Cycles per byte = 1097.49
AES-192-GCM-dec             50 KiB took 1.405 seconds,   35.587 KiB/s Cycles per byte = 1097.53
AES-256-GCM-enc             50 KiB took 1.623 seconds,   30.807 KiB/s Cycles per byte = 1267.69
AES-256-GCM-dec             50 KiB took 1.623 seconds,   30.807 KiB/s Cycles per byte = 1267.73
GMAC Default               478 KiB took 1.000 seconds,  478.000 KiB/s Cycles per byte =  81.71
3DES                       375 KiB took 1.003 seconds,  373.878 KiB/s Cycles per byte = 104.48
MD5                      10625 KiB took 1.000 seconds, 10625.000 KiB/s Cycles per byte =   3.67
SHA                       5400 KiB took 1.000 seconds, 5400.000 KiB/s Cycles per byte =   7.23
SHA-224                   1700 KiB took 1.014 seconds, 1676.529 KiB/s Cycles per byte =  23.30
SHA-256                   1700 KiB took 1.014 seconds, 1676.529 KiB/s Cycles per byte =  23.30
SHA-384                   1275 KiB took 1.009 seconds, 1263.627 KiB/s Cycles per byte =  30.91
SHA-512                   1275 KiB took 1.009 seconds, 1263.627 KiB/s Cycles per byte =  30.91
SHA-512/224               1275 KiB took 1.009 seconds, 1263.627 KiB/s Cycles per byte =  30.91
SHA-512/256               1275 KiB took 1.009 seconds, 1263.627 KiB/s Cycles per byte =  30.91
SHA3-224                   925 KiB took 1.006 seconds,  919.483 KiB/s Cycles per byte =  42.47
SHA3-256                   875 KiB took 1.008 seconds,  868.056 KiB/s Cycles per byte =  45.02
SHA3-384                   675 KiB took 1.010 seconds,  668.317 KiB/s Cycles per byte =  58.47
SHA3-512                   475 KiB took 1.019 seconds,  466.143 KiB/s Cycles per byte =  83.77
SHAKE128                  1075 KiB took 1.009 seconds, 1065.411 KiB/s Cycles per byte =  36.68
SHAKE256                   875 KiB took 1.008 seconds,  868.056 KiB/s Cycles per byte =  45.02
RIPEMD                    4325 KiB took 1.005 seconds, 4303.483 KiB/s Cycles per byte =   9.07
HMAC-MD5                 10525 KiB took 1.000 seconds, 10525.000 KiB/s Cycles per byte =   3.71
HMAC-SHA                  5375 KiB took 1.004 seconds, 5353.586 KiB/s Cycles per byte =   7.30
HMAC-SHA224               1675 KiB took 1.007 seconds, 1663.357 KiB/s Cycles per byte =  23.48
HMAC-SHA256               1675 KiB took 1.006 seconds, 1665.010 KiB/s Cycles per byte =  23.48
HMAC-SHA384               1250 KiB took 1.004 seconds, 1245.020 KiB/s Cycles per byte =  31.38
HMAC-SHA512               1250 KiB took 1.004 seconds, 1245.020 KiB/s Cycles per byte =  31.38
PBKDF2                       0 KiB took 1.092 seconds,    0.200 KiB/s Cycles per byte = 194936.64
RSA     2048   public        48 ops took 1.001 sec, avg 20.854 ms, 47.952 ops/sec
RSA     2048  private         2 ops took 9.438 sec, avg 4719.000 ms, 0.212 ops/sec
ECC   [      SECP256R1]   256  key gen         8 ops took 1.159 sec, avg 144.875 ms, 6.903 ops/sec
ECDHE [      SECP256R1]   256    agree         8 ops took 1.154 sec, avg 144.250 ms, 6.932 ops/sec
ECDSA [      SECP256R1]   256     sign         8 ops took 1.176 sec, avg 147.000 ms, 6.803 ops/sec
ECDSA [      SECP256R1]   256   verify         4 ops took 1.119 sec, avg 279.750 ms, 3.575 ops/sec
CURVE  25519  key gen         3 ops took 1.136 sec, avg 378.667 ms, 2.641 ops/sec
CURVE  25519    agree         4 ops took 1.512 sec, avg 378.000 ms, 2.646 ops/sec
ED     25519  key gen        73 ops took 1.004 sec, avg 13.753 ms, 72.709 ops/sec
ED     25519     sign        62 ops took 1.007 sec, avg 16.242 ms, 61.569 ops/sec
ED     25519   verify        40 ops took 1.033 sec, avg 25.825 ms, 38.722 ops/sec
Benchmark complete

If you have any feedback, questions, or require support, please don’t hesitate to reach out to us via facts@wolfSSL.com, call us at +1 425 245 8247, or open an issue on GitHub.

Download wolfSSL

If you are wondering if your part is supported by wolfSSL, the answer is “Yes!!” That said, what follows is an abbreviated incomplete list sorted by manufacturer:

Note: no matter how hard we try to make these lists, they will never be complete because the week after the list is made, there will be more to add.

If you do not see your part on this list, don’t worry. Please reach out to us at facts@wolfSSL.com, or call us at +1 425 245 8247 letting us know the details of your system and we can get you in touch with our porting experts. Chances are, it is already done!

If you do see your part and are wondering about benchmarking statistics you can also reach out to facts@wolfSSL.com for performance information. Check out our public benchmarks.

Download wolfSSL

We are excited to announce that the wolfSSL sniffer now supports TLS session decryption for recorded TLS traffic using a SSLKEYLOGFILE!

If you didn’t already know about our sniffer tool, it is a utility library built into wolfSSL that can be used to capture and decrypt live traffic or recorded PCAP traces. Previously, the sniffer could only decrypt traffic from sessions where either the static private key (RSA, ECC) or the ephemeral key (DHE, ECDHE) was known and able to be provided to the sniffer at runtime. This required keeping track of the private or ephemeral key files for every session you wanted to sniff, which was cumbersome for packet captures containing a large number of sessions, especially for TLS v1.3 where each session would require a new ephemeral key to decrypt.

If your server or client is able to generate a key log file (which wolfSSL can do with the `–enable-keylog-export` option), you can now simply register this file with the sniffer and the sniffer will be able to decrypt all applicable traffic in your packet capture, regardless of the cipher suite used!

To build wolfSSL with the sniffer enabled use the `–enable-sniffer` configure option. To enable key log file support in the sniffer, simply define `WOLFSSL_SNIFFER_KEYLOGFILE`:

./configure --enable-sniffer CFLAGS=“-DWOLFSSL_SNIFFER_KEYLOGFILE”

WolfSSL provides the snifftest demo application that demonstrates how to use the sniffer library to sniff traffic from both live and recorded packet captures. Using the snifftest app to sniff traffic from a packet capture with an associated key log file is as simple as running:

# Sniffs traffic from a server at 127.0.0.1 on port 11111
./snifftest -pcap /path/to/your.pcap \
            -keylogfile /path/to/your/keylogfile.log \
            -server 127.0.0.1 \
            -port 11111 

For more information and examples showing how to get started with the sniffer, please refer to the snifftest demo application and README.

As always, if you have questions on any of the above, please contact us at facts@wolfSSL.com, or call us at +1 425 245 8247.

Download wolfSSL

We are excited to announce that Daniel Stenberg, the creator of cURL, will be hosting a live stream on Mastering the cURL Command Line Training on August 31st at 9 am PT.

Check out: Mastering the cURL Command Line webinar

cURL, a versatile software project, enables you to securely transfer data using various protocols, such as FTP, FTPS, HTTP, HTTPS, and more.

During the live stream, Daniel will dive into the full potential of cURL and how you can utilize cURL in your projects to achieve maximum security in data transfer. Don’t miss out on this exclusive event to gain knowledge and technical skills directly from Daniel Stenberg, the creator of cURL!

Sneak peek of the live stream:

• An overview of the cURL project
• Command line essentials, including options, URLs, and advanced features
• Practical usage of cURL, covering topics like downloads, uploads, and transfer controls
• In-depth insights into TLS and proxy configurations
• Exploring HTTP protocols, including methods, response codes, and security
• Navigating FTP functionalities, including authentication and file transfers
• Looking at cURL’s future

During the webinar, you will discover the full potential of cURL, which can boost your projects, and learn technical skills.

If you have questions on any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.

Download wolfSSL