Month: April 2013

Many developers are now starting to think about IPv6 and what implications this will have on existing and future projects. IPv6 is becoming increasingly widespread and adoption will further continue to increase into the future.

As a developer, project manager, or curious individual, you may be faced with finding an SSL library which is compatible with IPv6. If so, rest assured! The wolfSSL embedded SSL library is compatible with both IPv4 and IPv6! The library itself has been designed to be IP neutral and work with either protocol version. In addition, we provide an easy-to-use build option to IPv6-enable our example applications for testing purposes.

To turn on IPv6 support when compiling wolfSSL and our example applications, use the “–enable-ipv6” build option:

./configure –enable-ipv6

Addresses beginning with fe80:: are link-local only. These addresses require an interface or scopeid suffix. For example, if ifconfig shows something similar to this:

inet6 fe80::62c5:47ff:fe97:ac2c%en1 prefixlen 64 scopeid 0x6

You could ping this address by doing either:

ping6 -I en1 fe80::62c5:47ff:fe97:ac2c

or

ping6 fe80::62c5:47ff:fe97:ac2c%en1

To start the wolfSSL example server using IPv6, remember to use the “-b” option to bind the server to any interface (unless localhost only is desired):

./examples/server/server -b

If an example wolfSSL example server was running on another link-local host (started with the “-b” option), a wolfSSL client could connect to it by doing something similar to:

./examples/client/client -h fe80::20c:29ff:fedc:e701%en1

Curious about how widespread IPv6 currently is? Google currently tracks IPv6 adoption here: http://www.google.com/ipv6/statistics.html, and you can see how many IPv6 hits/second Akamai is getting here: http://www.akamai.com/ipv6.

If you have any questions about how to use wolfSSL with IPv6, or general questions about using wolfSSL embedded SSL or CTaoCrypt in areas such as the Internet of Things, smart energy, home automation, M2M communication, or cloud services, please get in touch with us at facts@wolfssl.com.

Sick of all the tax day giveaways that you don`t really need, or worse, have to wait in line for?  How about a no wait release of CyaSSL 2.6.0 instead?  New features include:

– DTLS 1.2 featuring AEAD ciphers.  We`re excited about this feature and welcome any feedback.

-SHA-3 finalist Blake is now supported.  Blake2b is extremely fast and uses very little resources, so we like it a lot.

– Support for SHA-384 cipher suites including ECC ones is included as well.  And if you ever need to do HMAC with SHA-512 that`s now supported as well.

– The example client/server can now track memory and stack use with -t and –enable-stacksize respectively.

– IPv6 examples/tests now allow link-local with scopeid resolution and full ipv6 addresses instead of defaulting to localhost.  As before, use –enable-ipv6 to turn on IPv6 in the examples and don`t forget -b on the server to bind to any interface.

– CYASSL_GENERAL_ALIGNMENT manipulates the SSL input/output buffers to align crypto access for easier integration with hardware support.  SSL itself isn`t very friendly to alignment with 5 byte TLS headers and 13 byte DTLS buffers, but we think we have a good solution for this.

– Many new ./configure options including disable/enable for rsa, dh, dsa, md5, sha, arc4, null (ciphers), oldtls, and asn (no certs or public keys allowed).  ./configure options are all lowercase now for better consistency.  A cyassl/options.h header is also now generated during the ./configure process that allows a user to easily use the same settings/flags that cyassl itself was built with.

Please see the README and our on-line documentation for more information or feel free to contact us.

Happy Tax Day,
Team wolfSSL

TLS requires both end points to have received and processed their peer`s Change Cipher Spec and Finished messages before starting to transfer their bulk encrypted data. It needs the Finished message to validate its peer`s identify. To save one round-trip time, an endpoint after having sent its Finished message could start sending its encrypted data using that cipher specification.

wolfSSL currently does not directly support TLS False Start, but it is tolerant of a peer sending its data immediately after sending its Finished message. It just will not send encrypted data to its peer until it has completed its handshake.

Do you need wolfSSL to handle TLS False Start? Contact us at facts@wolfssl.com.

We would like to give our users an early heads up that our cryptography library, CTaoCrypt will soon be changing names to wolfCrypt. With the name change, there may be some changes to the existing crypto API. You’ll also begin to see changes in our documentation and website.

If you have any questions about the conversion, please feel free to contact us at facts@wolfssl.com.

Thanks,
– Team wolfSSL