We`ve implemented ChaCha20 allowing for the use of both 128 bit and 256 bit keys and are in the process of implementing Poly1305 into wolfSSL. Both crypt tools and a suite using the two are on schedule to be released by the end of the summer. The ChaCha20 and Poly1305 algorithms, originally developed by Bernstein, […]
Read MoreMore TagAuthor: wolfSSL
wolfSSL and Oculus Rift
Hi everyone, we’re curious if anyone is interested in using wolfSSL with the Oculus Rift? If you don’t know what an Oculus Rift is, it is a Next Generation Virtual Reality Technology for video games or any Virtual Reality Applications. You can learn more at the following URL: http://www.oculusvr.com/ If you have any questions, or […]
Read MoreMore TagwolfSSL and CyaSSL Users SAFE from Recent OpenSSL Security Advisories
OpenSSL released several security advisories yesterday: http://www.openssl.org/news/secadv_20140605.txt. None of these are attacks on the SSL/TLS protocols themselves. They are all implementation bugs. Most are critical bug fixes to DTLS (TLS over UDP). As a clean room implementation of SSL, wolfSSL does not use any OpenSSL code and is free from these defects. The most critical […]
Read MoreMore TagSupport for AES-NI in Visual Studio
Hi! We`ve been supporting AES-NI for a few years now. We`ve decided to extend that support to Visual Studio users. If you would like to use AES-NI with Visual Studio, then let us know. Beta code will be available shortly. Contact us at facts@wolfssl.com if you have questions.
Read MoreMore TagwolfSSL Releases IoT Demo of CyaSSL Working with Xively and mbed
For those of you interested in how CyaSSL fits into IoT, here is an example you should take a look at! We have prepared a demo with CyaSSL, Xively, and mbed. It runs on various mbed platforms with Ethernet connections, including NXP LPC1768 whose RAM size is as small as 32k for applications + 32k for […]
Read MoreMore TagwolfSSL Enforces Stack Usage Reduction
Understanding the stack and the heap are fundamental steps for all software developers. The importance of such understanding is inversely proportional to the amount of memory available on the platform, as both compete for a piece of the total memory space available on a system. In some cases the developer has the choice of when […]
Read MoreMore TagwolfSSL with TLS 1.3
Hi! Some of you know that the IETF working group on TLS is creating the specification for TLS 1.3. We plan to upgrade wolfSSL to the TLS 1.3 specification as soon as the spec is finalized, or even close to finalized. We are always aggressive with implementing the new TLS specifications, because we like to […]
Read MoreMore TagwolfSSL 3.0.0 Released
The new release of wolfSSL, v3.0.0, is now ready to download from our website. New features include: – FIPS release candidate – X.509 improvements that address items reported by Suman Jana with security researchers at UT Austin and UC Davis – Small stack size improvements, –enable-smallstack. Offloads large local variables to the heap. (Note this […]
Read MoreMore TagChaCha20 and Poly1305 for wolfSSL TLS
Hi! We`ve scheduled ourselves to implement ChaCha20 and Poly1305 into wolfSSL this summer. If you`re learning about what these are, see these links: http://cr.yp.to/mac.html https://www.imperialviolet.org/2013/10/07/chacha20.html We`re excited about this addition to our code. If you have comments, questions, or need it in our code sooner than this summer, then let us know! We can be […]
Read MoreMore TagwolfSSL’s Todd Ouska Comments on Heartbleed Bug
As a follow up to the recent Heartbleed bug in OpenSSL, Embedded Computing Design interviewed wolfSSL’s CTO, Todd Ouska for an article titled “Heartbleed: (Not) one in a million”. You can read the article at the following URL: http://embedded-computing.com/20937-heartbleed-not-one-in-a-million
Read MoreMore Tag