yaSSL made dramatic progress this year on a number of fronts, notably in open source community usage, embedded systems adoption, and technology improvements! Here’s what we’ve done this year, with an outline of our plans for the year to come in a blog post to follow:
1. Participated in 4 industry events, including OSCON, Embedded Live, Embedded Systems Computing, and ARM TechCon.
1. We launched a new and improved web site including new product support forums.
3. We’ve made significant incremental improvements to our documentation.
4. New partners! We’ll announce two new resale partners next week!
5. New technology partners: Canonical, Red Hat, Novell, Freescale and Express Logic.
6. Added a new Competitive Upgrade Program for wolfSSL. More details can be found at our Consulting Services page, under “Rip and Replace Competitive Upgrade“
Our long list of technology improvements includes:
1. ThreadX port. wolfSSL now supports building and running on ThreadX “out of the box”.
2. GoAhead Web Server port. wolfSSL now builds and runs with the GoAhead Web Server through the wolfSSL OpenSSL compatibility layer.
3. Sniffer. wolfSSL now has the ability to sniff an SSL session with the server`s private key and decode the application data.
4. Swig. wolfSSL has a swig interface file to allow multiple language access.
5. Python. wolfSSL now has some python bindings for CTaoCrypt.
6. AES-NI. wolfSSL now has AES-NI assembly optimizations for supported Intel hardware “Westmere”.
7. ARM. wolfSSL now has assembly optimizations for fastmath Public Key operations.
8. Mongoose. wolfSSL now builds and runs with the Mongoose Web Server with the wolfSSL OpenSSL compatibility layer.
9. JSSE. wolfSSL can now be a plug-in for system Java SSL Providers on OS X and Linux.
10. Android. wolfSSL is now ported to Android.
11. SHA-512. wolfSSL now supports the SHA-512 hash on systems with support for 64 bit types.
12. RIPEMD-160. wolfSSL now supports RIPEMD-160 as a hashing algorithm.
13. Key generation. wolfSSL now supports key generation.
14. Certificate generation. wolfSSL now supports certificate generation.
15. yaSSL Embedded Web Server. Our “own” web server with wolfSSL for security.
16. Low static memory. wolfSSL went from a default of 48kB static memory per SSL session to 4kB. (alpha)
17. Low dynamic memory. wolfSSL decreased runtime dynamic memory use. (alpha)
18. Porting. Increased the portability/flexibility of using wolfSSL on non-standard build environments with an OS header with defines that control the build.
19. No stdlib. wolfSSL can now be built without any C standard library headers, developers can now use their own “standard” library plug-in. (alpha)
20. Secure memcache. wolfSSL can now be used to secure memcache network communication including client/patient sensitive data/health records from internal and external snoopers locally and in the cloud. (beta)
21. Mbed. wolfSSL can be built and run on the Mbed microcontroller. (alpha)
We’re happy with our progress this year, and look forward to making even more improvements next year! We’ll be going into 2011 with greater resources and plan to move this project and business forward at an even faster rate.