RECENT BLOG 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.
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!
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
– PBKDF2 and PKCS #12 PBKDF
– 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 email@example.com.
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
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.
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.
AVERAGE SELECT QUERY TIMES
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.
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 firstname.lastname@example.org.
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:
– 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.
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 email@example.com, or through our support forums (http://wolfssl.com/forums).
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 – http://twitter.com/wolfSSL
3. Like us on Facebook – http://www.facebook.com/pages/YaSSL/147081235315602
4. Use the yaSSL Blog RSS Feed in your favorite RSS reader – http://www.wolfssl.com/feed
5. Follow us on LinkedIn – https://www.linkedin.com/company/wolfssl/
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 firstname.lastname@example.org.
The yaSSL Team
A post that recently caught our eye, titled “Dozens of exploits released for popular SCADA programs” by Dan Goodin at theregister.co.uk, 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 email@example.com.
Wikipedia (SCADA): http://en.wikipedia.org/wiki/SCADA
theregister.co.uk Article: http://www.theregister.co.uk/2011/03/22/scada_exploits_released/
Luigi Auriemma’s Post Listing Vulnerabilities: http://seclists.org/bugtraq/2011/Mar/187
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 www.yassl.com/yaSSL/Home.html
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 firstname.lastname@example.org.
CURL GitHub Page: https://github.com/bagder/curl
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.
PKCS (Public Key Cryptography Standards) refers to a group of standards created and published by RSA Security, Inc. PKCS#8 is designed as the Private-Key Information Syntax Standard, which is used to store private key information – including a private key for some public-key algorithm and set of attributes.
The PKCS#8 standard has two versions which describe the syntax to store both encrypted private keys and non-encrypted keys.
wolfSSL has had support for non-encrypted PKCS#8 for about a year. We`re currently in the process of adding support for encrypted PKCS#8. If you have any comments or questions about using PKCS#8 with wolfSSL, please let us know at email@example.com.
To learn more about the PKCS standards, or PKCS#8, please see the links below
- May 2020 (17)
- April 2020 (17)
- March 2020 (7)
- February 2020 (24)
- January 2020 (18)
- December 2019 (9)
- November 2019 (16)
- October 2019 (14)
- September 2019 (24)
- August 2019 (21)
- July 2019 (8)
- June 2019 (13)
- May 2019 (35)
- April 2019 (32)
- March 2019 (20)
- February 2019 (10)
- January 2019 (16)
- December 2018 (24)
- November 2018 (11)
- October 2018 (18)
- September 2018 (18)
- August 2018 (8)
- July 2018 (15)
- June 2018 (29)
- May 2018 (15)
- April 2018 (11)
- March 2018 (19)
- February 2018 (6)
- January 2018 (11)
- December 2017 (5)
- November 2017 (12)
- October 2017 (7)
- September 2017 (8)
- August 2017 (6)
- July 2017 (11)
- June 2017 (8)
- May 2017 (10)
- April 2017 (5)
- March 2017 (7)
- February 2017 (1)
- January 2017 (8)
- December 2016 (3)
- November 2016 (2)
- October 2016 (18)
- September 2016 (8)
- August 2016 (5)
- July 2016 (4)
- June 2016 (11)
- May 2016 (4)
- April 2016 (5)
- March 2016 (4)
- February 2016 (12)
- January 2016 (6)
- December 2015 (4)
- November 2015 (6)
- October 2015 (6)
- September 2015 (5)
- August 2015 (8)
- July 2015 (7)
- June 2015 (9)
- May 2015 (1)
- April 2015 (4)
- March 2015 (13)
- January 2015 (6)
- December 2014 (7)
- November 2014 (3)
- October 2014 (2)
- September 2014 (11)
- August 2014 (6)
- July 2014 (9)
- June 2014 (11)
- May 2014 (11)
- April 2014 (9)
- March 2014 (3)
- February 2014 (3)
- January 2014 (5)
- December 2013 (9)
- November 2013 (4)
- October 2013 (7)
- September 2013 (3)
- August 2013 (9)
- July 2013 (7)
- June 2013 (4)
- May 2013 (8)
- April 2013 (4)
- March 2013 (2)
- February 2013 (3)
- January 2013 (9)
- December 2012 (13)
- November 2012 (5)
- October 2012 (7)
- September 2012 (4)
- August 2012 (6)
- July 2012 (4)
- June 2012 (3)
- May 2012 (6)
- April 2012 (7)
- March 2012 (2)
- February 2012 (5)
- January 2012 (7)
- December 2011 (5)
- November 2011 (7)
- October 2011 (6)
- September 2011 (6)
- August 2011 (5)
- July 2011 (2)
- June 2011 (8)
- May 2011 (12)
- April 2011 (4)
- March 2011 (12)
- February 2011 (9)
- January 2011 (13)
- December 2010 (17)
- November 2010 (12)
- October 2010 (14)
- September 2010 (11)
- August 2010 (20)
- July 2010 (14)
- June 2010 (7)
- May 2010 (1)
- January 2010 (2)
- November 2009 (2)
- October 2009 (1)
- September 2009 (1)
- May 2009 (1)
- February 2009 (1)
- January 2009 (1)
- December 2008 (1)