Category: Uncategorized

wolfSSL is now available as a crypto provider for KoanLogic’s SCS library, LibSCS. SCS, a small cryptographic protocol layered on top of the HTTP cookie facility [RFC6265], allows its users to produce and consume authenticated and encrypted cookies, as opposed to usual cookies, which are un-authenticated and sent in clear text.

From the LibSCS README, “By having a non-tamperable proof of authorship attached, each SCS cookie can always be validated by the originator, making it possible for a server to handle clients` session state without the need to store it locally. In fact, an SCS enabled server could completely delegate the application state storage to the client (e.g. a web browser) and use it, in all respects, as a remote storage device. The result of the cryptographic transformations applied to state data can be used to ensure that its information authenticity and confidentiality attributes are the same as if they were stored privately on server-side.”

You can build LibSCS with wolfSSL by running the following commands. You must have KoanLogic’s makl installed on your development machine (http://koanlogic.com/makl/) to build the package. See the libscs README and INSTALL files for more detailed instructions.

makl-conf –crypto=cyassl
makl

libscs GitHub repository: https://github.com/koanlogic/LibSCS

If you have any questions about wolfSSL with LibSCS, please contact KoanLogic (info@koanlogic) or yaSSL (info@yassl.com).

yaSSL currently secures over 50 million points on the internet.  We don’t talk about who is using CyaSSL, for obvious reasons, but the numbers are big and growing.

We take our work seriously, and hope you feel comfortable with our efforts.  We endeavor to build a business, a community, and do the right thing.  We welcome your feedback.  If you believe that we have failed at some point, then let us know.  We’ll correct it.  We’re open source and open minded about what you have to say.  Contact us at info@yassl.com and let us know how we’re doing!

Did you know that the wolfSSL embedded SSL library supports FreeRTOS and OpenRTOS? FreeRTOS is a real-time operating system for embedded devices which is designed to be both small and simple. With an incredibly large user base, FreeRTOS/OpenRTOS supports 27 architectures and is downloaded from over 77 thousand times every year!

Just like wolfSSL, FreeRTOS is open source, royalty free, and very portable. To build wolfSSL for FreeRTOS, uncomment the #define for FREERTOS in ./cyassl/ctaocrypt/settings.h.

You can find a full list of FreeRTOS features on the FreeRTOS/OpenRTOS website. To learn more about wolfSSL, please visit the wolfSSL product page. If you have any questions about using wolfSSL with FreeRTOS, please contact us at info@yassl.com.

FreeRTOS / OpenRTOS: http://www.freertos.org

Our 2011 annual report is now up on MarketWatch.com (see link below). yaSSL saw some great progress in 2011 which was very exciting! We’re looking forward to 2012 and seeing what the new year brings. If you have any questions about our annual report, please let us know at info@yassl.com.

yaSSL 2011 Annual Report (MarketWatch):
http://www.marketwatch.com/story/yassl-marks-growth-of-embedded-ssl-in-findings-from-2011-annual-report-2012-01-23 (as of 26 March 2018 at 9:26am MDT, this link no longer works and has no alternative).

Thanks!
Team yaSSL

As the security of individual field devices (sensors, transmitters, acuators, etc.) is often overlooked, these devices can provide a target for cyber attacks. This article by Matt Luallen of Control Engineering explains this fact in more detail – once again reminding us that security of such devices should not be taken lightly. Luallen states that “If your technicians can configure a field device through the control system, dedicated handheld tools, or by plugging in a laptop to the network, an attacker can do the same thing if he follows the right path.”

Secure communication is an important building block of device security. The wolfSSL embedded SSL library has been designed for resource-constrained embedded systems and can easily be added to your device. To learn more about wolfSSL and how it can help with your device security, feel free to contact us at facts@wolfssl.com.

Security At The Device Level: http://www.controleng.com/single-article/security-at-the-device-level/

yaSSL has made great progress 2011!  Company growth, active partnerships, technical improvements, and our community have all made great strides forward.  We are very happy with the results of 2011 and look forward to an exciting year in 2012!  Looking to 2012, we are planning ongoing improvements to our technology and have doubled our technical resources in order to better serve our users in 2012.  

Listed below is an overview of our progress in 2011.

Business and Company Progress

1.  We participated and/or exhibited in the following events: FOSDEM, ESC Silicon Valley, O`Reilly MySQL Conference & Expo, RSA Conference, Game Developers Conference, Infosecurity Europe, OSCON, ESC Boston, and the ARM Technology Conference

2.  We gave presentations at both FOSDEM 2011 (Lightning Talk) and the 2011 O`Reilly MySQL Conference (Securing MySQL with a Focus on SSL) and published an article in the Linux Journal (Installing an Alternate SSL Provider on Android). Our presentations can be found on our Media page.

3.  We made significant improvements to our documentation (including the wolfSSL Manual, wolfSSL API Reference, and SSL Tutorial) and to our website.

4.  Our customer base doubled in 2011 and we increased our revenues by 5X.

Meaningful progress with our partner community:

1.  ARM:  wolfSSL is now included in the ARM / Avnet Embedded Software Store (www.embeddedsoftwarestore.com).
2.  Intel:  Continued a successful partnership with Intel, along with becoming a general member of the Intel Embedded Alliance
3.  We added Security Innovation and SkypeKit as a new partners.
4.  We added KoanLogic as a new partner.

wolfSSL Technical Progress

Feature highlights from our five releases of the wolfSSL embedded SSL library in 2011 include:

1.  Added Elliptic Curve (ECC) cipher suites to wolfSSL
2.  Added support for ECC, EC-DSA, and EC-DH to our CTaoCrypt crypto library
3.  Better TLS 1.2 support through more comprehensive interoperability testing with other SSL implementations
4.  Added SHA256 cipher suites and certificate signatures
5.  Added PKCS8 private key encryption support
6.  Added Password based key derivation function 2 (PBKDF2)
7.  Added PKCS #12 PBKDF support as part of our plan to get to full PKCS12 support
8.  Included UID parsing for x509 certificates
9.  Included runtime memory hooks for users wanting to change memory functions at runtime
10.  Added runtime hooks for customizable logging ability
11.  Added compiler function visibility and better naming for less namespace pollution
12.  Created simpler header structure for users
13.  Added make test support
14.  CTaoCrypt runtime library detection ability
15.  Added AES counter (CTR) mode
16.  EDH on both client and server sides
17.  Made NTRU Cipher Suites available

yaSSL Embedded Web Server Progress

1.  Released version 0.2 with bug fixes and feature enhancements
1.  Improved documentation and examples

Porting Progress

1.  CURL port.  wolfSSL can now be built with CURL (as a build option).
2.  Mbed Release.  wolfSSL was ported to Mbed in late 2010 and is now available for the Mbed cloud compiler.
3.  KLone Web Application Framework.  wolfSSL is now ported to the KLone Web Application Framework by KoanLogic.
4.  memcached patch.  wolfSSL now provides SSL security for memcache.
5.  FreeRTOS support.  wolfSSL now supports FreeRTOS/OpenRTOS.
6.  Haiku OS.  wolfSSL now works with the Haiku Operating System.
7.  lwIP support.  wolfSSL now supports running on top of lwIP.
8.  Microchip pic32 support.  wolfSSL now supports running on the pic32.
9.  reSIPprocate port
10.  We now support wpa_supplicant as a compile time option.
11.  Added hostapd support
12.  Apple TV port:  wolfSSL and yasslEWS now can be run on the Apple TV.
13.  Added wolfSSL crypto provider to MIT Kerberos library.
14.  wolfSSL Android NDK package.  wolfSSL can now be used in Android NDK applications.
15.  Ported MIT Kerberos to Android using Google’s Android NDK.

Code & Community

1.  Migrated wolfSSL code to GitHub
2.  Introduced the yaSSL Support Forums
3.  Added BMX6 to the wolfSSL Community

We are looking forward to the upcoming year and sharing new features and technology improvements with our embedded SSL users and community.

Are you interested in using the yaSSL Embedded Web Server in your project or on your device but have discovered that it currently lacks support for your desired platform? yaSSL offers a porting service for the yaSSL Embedded Web Server for just this occasion.

If you are interested in having us port the yaSSL Embedded Web Server to your platform, please contact us at info@yassl.com for more information about cost and time estimates.

We receive a lot of questions about the origins of the CyaSSL and CTaoCrypt 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 was Born in the USA and written by US citizens.

If you have any additional questions about the origins of the CyaSSL embedded SSL library, please contact us at info@yassl.com

Hi!  Would you be interested in wolfSSL ported into Dropbear? We have been thinking about putting wolfSSL into Dropbear SSH, and would like your feedback.  Contact us at info@yassl.com if you think wolfSSL should be ported into Dropbear.

Many of our users are curious about how the wolfSSL embedded SSL library will perform on a specific hardware device or in a specific environment. Because of the wide variety of different platforms and compilers used today in embedded, enterprise, and cloud-based environments, it is hard for us to give generic performance calculations across the board.

To help our users and customers in determining SSL performance for wolfSSL / CTaoCrypt, we provide a benchmark application which is bundled with wolfSSL. wolfSSL uses the CTaoCrypt cryptography library for all crypto operations by default. Because the underlying crypto is a very performance-critical aspect of SSL/TLS, our benchmark application runs performance tests on CTaoCrypt’s algorithms.

The benchmark utility is located in ctaocrypt/benchmark. Typical output may look like:

./ctaocrypt/benchmark/benchmark
AES 5 megs took 0.033 seconds, 149.84 MB/s
ARC4 5 megs took 0.017 seconds, 297.23 MB/s
HC128 5 megs took 0.004 seconds, 1185.10 MB/s
RABBIT 5 megs took 0.011 seconds, 453.14 MB/s
3DES 5 megs took 0.236 seconds, 21.18 MB/s

MD5 5 megs took 0.011 seconds, 444.13 MB/s
SHA 5 megs took 0.019 seconds, 261.73 MB/s
SHA-256 5 megs took 0.041 seconds, 122.98 MB/s
SHA-512 5 megs took 0.023 seconds, 213.44 MB/s

RSA 2048 encryption took 0.11 milliseconds, avg over 100 iterations
RSA 2048 decryption took 2.36 milliseconds, avg over 100 iterations
DH 2048 key generation 0.88 milliseconds, avg over 100 iterations
DH 2048 key agreement 0.92 milliseconds, avg over 100 iterations

This is especially useful for comparing the public key speed before and after changing the math library. You can test the results using the normal math library (./configure), the fastmath library (./configure –enable-fastmath), and the fasthugemath library (./configure –enable-fasthugemath).

As always, please contact info@yassl.com with any questions or comments.