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 2.0 New Features – Part 1

Here`s a more detailed report on some of the new features that are in the recent wolfSSL 2.0 release. wolfSSL 2.0 RC1 is available for download from our Downloads page.

* SHA-256 cipher suites are now supported. The new suites include:


No action is needed to include these suites, they`re in by default.

* Root certificate verification has been added. wolfSSL used to require all certificates in the chain to be trusted in order to do a verification. Now, only the top or root certificate of the chain is required to be loaded as a trusted certificate in order to properly verify the chain.

* PKCS #8 private key encryption. wolfSSL now support PKCS #8 private encrypted keys. Supported formats include PKCS #5 version 1 – version 2 and PKCS #12. Types of encryption available include DES, 3DES, RC4, and AES.

* Serial number retrieval for x509. A serial number of any length can now be extracted with wolfSSL using the extension function:

int wolfSSL_X509_get_serial_number(X509* x509, byte* buffer, int* inOutSz)

buffer will be written to with at most *inOutSz bytes on input. After the call, if successful (return of 0), *inOutSz will hold the actual number of bytes written to buffer. A full example is included cyassl_test.h.

* PBKDF2 and PKCS #12 PBKDF. wolfSSL used to only support password based key derivation function 1. Now it additionally support version 2 and the PBKDF version from PKCS #12. Use is the same as the original and the function prototypes look like:

int PBKDF2(byte* output, const byte* passwd, int pLen, const byte* salt, int sLen, int iterations, int kLen, int hashType);

int PKCS12_PBKDF(byte* output, const byte* passwd, int pLen, const byte* salt, int sLen, int iterations, int kLen, int hashType, int purpose);

output contains the derived key, passwd holds the user password of length pLen, salt holds the salt input of length sLen, iterations is the number of iterations to perform, kLen is the desired derived key length, and hashType is the hash to use which can be MD5, SHA1, or SHA2.

A full example is included in ctaocrypt/src/test.c. Please email us at or with any questions regarding the above feature additions, or wolfSSL in general.

yaSSL Live from ESC

The yaSSL team is live from ESC Silicon Valley – located at booth 2322. This morning and afternoon has been bustling with activity after attendees lined up for the free tote bag giveaway. If you’re at ESC 2011, stop by our booth to visit. We’ll be talking about how you can add SSL/TLS to your embedded application or device through our wolfSSL library as well as our yaSSL Embedded Web Server.

We hope to see you here!

Team yaSSL

wolfSSL 2.0.0 Release Candidate 1 is Now Out

wolfSSL 2.0.0 Release Candidate 1 is now available for download on our website.  The release is chunk full of new features including:

– SHA-256 cipher suites
– Root Certificate Verification (instead of needing all certs in the chain)
– PKCS #8 private key encryption (supports PKCS #5 v1-v2 and PKCS #12)
– Serial number retrieval for x509
– UID parsing for x509
– SHA-256 certificate signatures
– Client and server can send chains (SSL_CTX_use_certificate_chain_file)
– CA loading can now parse multiple certificates per file
– Dynamic memory runtime hooks
– Runtime hooks for logging
– EDH on server side
– More informative error codes
– More informative logging messages
– Version downgrade more robust (use SSL_v23*)
– Shared build only by default through ./configure
– Compiler visibility is now used, internal functions not polluting namespace
– Single Makefile, no recursion, for faster and simpler building
– Turn on all warnings possible build option, warning fixes

Stay tuned for a few posts this week giving more details about all the new features.

Because of all the new features and the multiple OS, compiler, feature-set options that wolfSSL allows, there may be some configuration fixes needed. Please send any comments or questions to

MySQL SSL Performance Benchmarking

Have you ever been curious about what performance impact SSL has when used with MySQL? We recently benchmarked SSL vs non-SSL performance in MySQL using yaSSL. yaSSL is bundled with source distributions of MySQL by default. We compared both the footprint size as well as average query times for SELECT queries (measured with the sysbench tool).

Our findings were part of a presentation on MySQL security practices along with an introduction to SSL and TLS. It was titled “Securing MySQL with a Focus on SSL“, and was recently presented at the 2011 O`Reilly MySQL Conference & Expo. If you missed our presentation, or if you would like to download the slides as a reference, you can find them in PDF format on our Media Page.

Our benchmark machine was an Apple Macbook Pro, with the following specs:

Apple Macbook Pro
Intel Core 2 Duo
2.33 GHz
4 MB L2 Cache, 2GB Memory, 667 MHz Bus Speed


The difference in footprint size between an installation of MySQL with SSL support versus one without SSL is very small (about 5%). There are two directories containing size differences: the `lib` and `bin` directories, with size comparisons as shown in Figure 1, below.

Figure 1
Footprint size comparison of MySQL with SSL (Green) and MySQL without SSL (Red). This was calculated by running the “du” command inside the MySQL installation directory after a new install.

Looking at average query times, Figure 2 shows a breakdown of average query time (ms) comparisons for varying number of concurrent client connections. Looking at one sample specifically, we can see that for a client concurrency of eight, there is a 16.9% increase in the average query time when connections are using SSL.

Figure 2
Average query times (in ms) for varying number of concurrent client connections. Results were obtained by using the sysbench tool on a new MySQL installation.

These tests were run on a laptop using the sysbench tool. Speeds on enterprise platforms will vary. If you have any questions about our findings or methodology for testing, please email us directly at

Securing MySQL with a Focus on SSL

As you may know, we recently gave a presentation titled “Securing MySQL with a Focus on SSL” at the 2011 O`Reilly MySQL Conference & Expo. We had a great time, met a bunch of awesome people, and learned a lot. Now that the conference is over, we`ve posted our slides to our Media page as a resource, here.

Our presentation covers the basics of securing a new MySQL installation, goes over an introduction of how SSL and TLS work, and touches on data encryption as well. A general outline is below:

MySQL Security
– Common Attacks & Vulnerabilities
– Good Security Practices for MySQL

– Overview of SSL and TLS
– Configuring and Building MySQL with SSL
– MySQL SSL Command Options
– SSL Certificate Creation
– Performance Comparison
Additional Security Concerns
– Data Storage and Encryption

If you find any errors in our presentation, or see things that you think should be added, please let us know. Stay tuned for a summary of our SSL performance results.

Team yaSSL

yaSSL 2011 Q1 Report

yaSSL has made substantial progress in Q1 of 2011, including improvements and expansions in the areas of standards support, new ciphers, code repositories, and new community activity. We like to keep our users up to date about our progress. An overview of yaSSL accomplishments and activities for Q1 can be seen below:

– SHA-256 Cipher Suites
– PKCS8 Private Key Encryption Support
– Password-based key derivation function 2
– Better TLS 1.2 support

yaSSL Embedded Web Server
– Release 0.2. Added increased documentation, bug fixes, and examples.

– Mbed Release. wolfSSL is now ported to mBed and available for their cloud compiler.
– CURL port. wolfSSL can now be built with CURL (as a build option).
– memcached patch. wolfSSL now provides SSL security for memcache.
– reSIPprocate port
– Haiku OS. wolfSSL now works with the Haiku Operating System.

Code & Community
– Migrated wolfSSL code to GitHub
– Introduced the yaSSL Support Forums
– Added BMX6 to the wolfSSL Community
– Expanded and Grew our Partnership with Intel
– Revived and updated our Freshmeat Accounts

Conference & Expo`s
– RSA Conference
– O`Reilly MySQL Conference & Expo
(Presentation: Securing MySQL with a Focus on SSL)

If you have questions about items in the above list, or would like more information on yaSSL products, please contact directly at, or through our support forums (

Team yaSSL

Keep Updated on yaSSL News

The yaSSL crew believes that keeping our users up to date on company and product news is very important. With this in mind, we have tried to offer many forms and outlets for you to follow our news. Currently, you can read our news and keep up to date in any of the following ways:

1. Reading the yaSSL Blog – News directly from the source
2. Follow us on Twitter –
3. Like us on Facebook –
4. Use the yaSSL Blog RSS Feed in your favorite RSS reader –
5. Follow us on LinkedIn –

If there is a different method that you think would be more beneficial for you to receive our news, please let us know, and we’ll think about implementing it. As always, we love to hear feedback from our users about our products, website, or news we’ve posted. Please send any comments or suggestions to

The yaSSL Team

Security of SCADA Programs

A post that recently caught our eye, titled “Dozens of exploits released for popular SCADA programs” by Dan Goodin at, reveals that SCADA systems may not be as secure as some people think.  In the article, Luigi Auriemma, one of the researchers who released the vulnerabilities, stated that “SCADA is a critical field but nobody really cares about it.”

SCADA, or “Supervisory Control and Data Acquisition”, refers to industrial control systems which monitor, control and collect data from industrial, infrastructure, or facility-based processes.  SCADA systems are found at the heart of many industries including Water Management Systems, Electric Power, Traffic Signals, Mass Transit Systems, and Manufacturing Systems.  As you could guess, an exploit in one of these areas’ industrial processes could have an immense impact, and should be taken seriously.

Not only do SCADA systems need to be concerned with remote code execution, but the security of data being transferred between the SCADA sensor and the host computer is very important as well.  To secure this data link, SCADA systems may use SSL/TLS to encrypt all traffic between the sensor and server.  CyaSSL is an ideal SSL/TLS solution for this type of system.  The CyaSSL embedded ssl library has been optimized for embedded environments and devices, and is able to provide the best possible SSL/TLS encryption while offering a small footprint and fast speeds.

For more information about the released SCADA vulnerabilities, see the links below.  For information regarding the CyaSSL embedded SSL/TLS library, please contact us at

Wikipedia (SCADA): Article:

Luigi Auriemma’s Post Listing Vulnerabilities:

wolfSSL Build Option in CURL

With the next release of CURL and libcurl, 7.21.5, there will be support for the wolfSSL Embedded SSL Library. This allows CURL to leverage the benefits of the wolfSSL library – including its small footprint, optimizations for embedded environments, and support for TLS 1.2.

First released in 1997, CURL (“Client for URLs”) is a command line tool (along with libcurl, a library) for transferring data using various protocols with URL syntax. Some of the supported protocols include DICT, FILE, FTP(S), GOPHER, HTTP(S), IMAP(S), LDAP(S), POP3(S), RTMP, RTSP, SCP, SFTP, SMTP(S), TELNET, AND TFTP. Being extremely portable, free, feature rich, supported, and fast, it is a go-to tool and library for a large number of users.

Basic CURL syntax simply involves typing “curl” at the command line followed by the URL of the output to retrieve. For example, to retrieve yaSSL’s home page, the following command could be issued:

shell> curl

After downloading the CURL source (see link below), wolfSSL support can be enabled by building CURL using the “–with-cyassl” build option. While enabling wolfSSL, OpenSSL must be disabled by using the “–without-ssl” build option in addition:

shell> ./configure –without-ssl –with-cyassl

This assumes that wolfSSL has been installed in the default directory (/usr/local/cyassl). If wolfSSL has been installed in a different directory, it can be specified by appending it to the wolfSSL build option: “–with-cyassl=PATH”. For more information about wolfSSL and CURL, please email

CURL GitHub Page:

Born in the USA!

Hi!  We’ve received a lot of questions recently about the origins of the wolfSSL software package.  We get asked where was it developed, and by who?  The questions usually come from US government agencies and their contractors.  Simply stated, mes amis, wolfSSL was Born in the USA and written by US citizens

Posts navigation

1 2 3 77 78 79 80 81 82 83 92 93 94

Weekly updates


Latest Tweets