We are often asked about how we test wolfSSL. At this point, we believe we have testing that is quite robust, but we acknowledge that there is no such thing as perfect testing. With that knowledge in mind, we have the goal of incrementally improving and automating our testing rigs over time. Our overriding goal […]
Read MoreMore TagAuthor: wolfSSL
Reduce Packet Data Overhead in M2M applications with wolfSSL
Many of our customers use the wolfSSL lightweight SSL/TLS package in M2M applications where usage is charged based on data transfer. As such, it becomes important to minimize data transfer rates when running SSL. Here are a few thoughts on how wolfSSL M2M users can minimize data packet overhead when implementing our embedded SSL: 1) […]
Read MoreMore TagUsing Maximum Fragment Length with wolfSSL
Did you like the addition of SNI in the last wolfSSL release? If so, you probably will like the Maximum Fragment Length extension as well! TLS specifies a fixed maximum plaintext fragment length of 2^14 bytes. It may be desirable for constrained clients to negotiate a smaller maximum fragment length due to memory or bandwidth […]
Read MoreMore TagGearman Now Supports wolfSSL
We would like to announce to our community that Gearman, a framework designed to distribute tasks to multiple machines or processes, now has SSL/TLS support using the wolfSSL lightweight SSL library. From the Gearman site, Gearman “allows you to do work in parallel, to load balance processing, and to call functions between languages. It can […]
Read MoreMore TagwolfSSL Release 2.7.0 Now Available
The bi-monthly release of wolfSSL, 2.7.0, is now ready to download from our website. New features include: – SNI (Server Name Indication) for both the client and server with –enable-sni– KEIL MDK-ARM project files in IDE/MDK-ARM– Domain name match checks now included wildcard and Subject altname checks by default– More consistent error returns across all […]
Read MoreMore TagBorn in the USA!
We receive a lot of questions about the origins of the CyaSSL lightweight SSL library and wolfCrypt software packages. We get asked where they were developed, and by who? These questions usually come from US government agencies and their contractors. Simply stated, mes amis, CyaSSL and wolfCrypt were Born in the USA and written by US citizens. If […]
Read MoreMore TagDocumentation for using wolfSSL with Keil MDK-ARM
The wolfSSL lightweight SSL package is used by a healthy chunk of Keil users. In the interest of better enabling our Keil MDK-ARM users, we`ve added MDK-ARM 4 support and documented it here: http://www.yassl.com/yaSSL/cyassl-keil-mdk-arm.html. What`s next? MDK-ARM 5 support. MDK-ARM 5 will make setup and integration even easier! Let us know if you are interested […]
Read MoreMore TagwolfCrypt and wolfSSL Separation
Up to now, wolfCrypt cryptography library users have had to use it as a part of wolfSSL. We are now embarking on the project to separate the two, and when finished should have a separate wolfCrypt download for our users that only need to use our crypto. Our goals are to make the separate downloads […]
Read MoreMore TagUsing Server Name Indication (SNI) with wolfSSL
Have you ever wondered how to use SNI with the wolfSSL embedded SSL library? SNI is useful when a server hosts multiple ‘virtual’ servers at a single underlying network address. It may be desirable for clients to provide the name of the server which it is contacting. To enable SNI with wolfSSL you can simply […]
Read MoreMore TagwolfSSL Support for Microchip TCP/IP Version 6
Are you interested in using the wolfSSL lightweight SSL/TLS library with version 6 of the Microchip TCP/IP stack? If so, you’re in luck! We recently added support for version 6 to wolfSSL. Now wolfSSL supports running on top of either version 5 or version 6 of the stack. We have updated not only our library […]
Read MoreMore Tag