wolfSSL at Docker Hub

We at wolfSSL are pleased to announce that now you can use wolfSSL directly from Docker!

In a few words, Docker is a tool designed to make it easier to create, deploy, and run applications by using containers. Containers are like virtual machines, but way more lighter as the container shares some resources with the hosting machine.

We created a collection of wolfSSL containers targeting the following OSs: Debian, Ubuntu, Alpine Linux, CentOS

There are 3 different flavors of containers we have created based on each OS: lib, test and examples

wolfssl/wolfssl ubuntu-examples 9198e6d82596 127MB
wolfssl/wolfssl ubuntu-test     ba5ca8ca4359 351MB
wolfssl/wolfssl ubuntu-lib      125125eea7ab 126MB
ubuntu          latest          2d696327ab2e 122MB

wolfssl/wolfssl debian-examples cd066ee3b5db 106MB
wolfssl/wolfssl debian-test     5a3edb3a2a20 356MB
wolfssl/wolfssl debian-lib      3086ef0f07b6 105MB
debian          latest          72ef1cf971d1 100MB

wolfssl/wolfssl centos-examples 37687e96d5b9 222MB
wolfssl/wolfssl centos-test     359d4195ca53 392MB
wolfssl/wolfssl centos-lib      a8c6cafd6205 221MB
centos          latest          196e0ce0c9fb 197MB

wolfssl/wolfssl alpine-examples 490120f86d61 8.74MB
wolfssl/wolfssl alpine-test     52b698631bec 228MB
wolfssl/wolfssl alpine-lib      692a0c26cda6 7.97MB
alpine          latest          76da55c8019d 3.97MB

The -lib images contain only the wolfSSL binaries, while -examples also contain the test examples and -test also contain wolfSSL’s source code.

You can find further information on how to run wolfSSL examples on a docker container in our docker hub page: https://hub.docker.com/u/wolfssl/

And here is a quick example, server in the left tab and the client in the right tab:

References:

wolfSSL Docker repository: https://hub.docker.com/r/wolfssl/wolfssl/
Wikipedia Container article: https://en.wikipedia.org/wiki/Operating-system-level_virtualization

wolfSSL at Microchip MASTERs 2018

wolfSSL will be attending and exhibiting at the 22nd Annual Worldwide Microchip MASTERS Conference in Phoenix, AZ.  The main conference will be held Wednesday morning (8/22) through Saturday at noon (8/25).  wolfSSL will be set up in the Exhibitor Lobby ready to answer your questions about securing your projects with wolfSSL SSL/TLS, wolfCrypt, wolfSSH, wolfMQTT, and more!  wolfSSL also supports TLS 1.3, and will have TLS 1.3 stickers on hand!

Stop by our booth at the Exhibitor Lobby to say hello, or email us at info@wolfssl.com to schedule a meeting time.  We’ll look forward to seeing you there!

stunnel support for TLS 1.3 using wolfSSL

Did you know that wolfSSL maintains a port of stunnel which includes wolfSSL support, and now supports TLS 1.3?

What is stunnel?

stunnel is a lightweight TLS proxy, designed to add SSL/TLS encryption to unsecured applications without changes to the program’s source code.  Licensed under GNU GPLv2 and with an alternative commercial option, stunnel can be utilized to secure a host of different applications, including: mail exchange (SMTP, IMAP, POP3), web hosting (HTTP), remote shell, and virtually any other unprotected protocol desired.

TLS 1.3 Support!

Porting stunnel to use wolfSSL’s embedded SSL/TLS library means taking advantage of wolfSSL’s minimal footprint and high speed crypto implementation to increase performance and decrease required resources when compared to other SSL/TLS libraries. Not only that, but using wolfSSL with stunnel combines these benefits with the peace of mind that your application is secured by a progressive, transparent, and stable SSL/TLS library – known for its quality, integrity and efficiency.

The wolfSSL embedded SSL/TLS now includes support for TLS 1.3, which gives stunnel+wolfSSL users access to TLS 1.3!  TLS 1.3 improves upon the SSL/TLS protocol by removing old insecure algorithms and changing the TLS handshake to increase security and reduce round trips.

To build wolfSSL for use with stunnel and TLS 1.3 support, simply configure wolfSSL with:

$ ./configure --enable-stunnel --enable-tls13

from wolfSSL`s main directory, then make and make install.

For a version of stunnel that links to the wolfSSL library, and for more information, contact us at info@wolfssl.com.

wolfCrypt v4.0 FIPS 140-2 Certificate News

Good news from wolfSSL Inc! The upcoming update to our cryptography library, wolfCrypt v4.0, is on the NIST CMVP Modules in Process list and is in the Coordination phase. Our FIPS 140-2 revalidation certificate is just around the corner. Included on the new certificate will be key generation of RSA, ECC, DH keys; SHA-3 and HMAC with SHA-3; CMAC; AES-GCM with internally generated IVs and externally supplied IVs; and use of RDSEED, AES-NI, and AVX1/2 with Intel processors. All the algorithms from our original certificate #2425 are also included. For more information about our new FIPS 140-2 certificate, please contact us at fips@wolfssl.com.

wolfSSH v1.3.0 Released

wolfSSL has released wolfSSH v1.3.0 to the public! Included in this release are two major features, SCP and SFTP. wolfSSH can now act as a server for copying files with SCP. We can also act like a client or server for SFTP connections! Now you can copy new firmware or configuration files to your embedded device with the ease of a file copy.

Also included are several small bug fixes and improvements.

wolfSSH was developed to with work with our wolfCrypt cryptography library. If you want FIPS 140-2, wolfSSH will seamlessly work with the FIPS version of wolfCrypt.

For more information about wolfSSH, wolfSSL, or wolfCrypt, please email info@wolfssl.com or contact sales@wolfssl.com. If you want to know more about wolfSSH with wolfCrypt FIPS, contact fips@wolfssl.com.  You can download wolfSSH 1.3.0 today from our download page!

wolfSSL is at Black Hat USA 2018!

wolfSSL is exhibiting at Black Hat USA this week in Las Vegas, NV!  Today is the last day of the conference, so make sure to stop by our booth (#1327) to talk with our experts about TLS 1.3, TPM and secure enclaves, embedded security, embedded SSL/TLS, MQTT, SSH, and more!  We also have TLS 1.3 stickers on hand!

If you would like to set up a specific meeting time either on or off the show floor, email us at info@wolfssl.com.

wolfSSL Intel SGX (#SGX) + FIPS 140-2 (#FIPS140)!

wolfSSL is pleased to announce the following addition to the wolfSSL FIPS certificate!

Debian 8.7.0 Intel ® Xeon® E3 Family with SGX support Intel®x64 Server System R1304SP
Windows 10 Pro Intel ® Core TM i5 with SGX support Dell LatitudeTM 7480

The wolfCrypt FIPS validated cryptographic module has been validated while running inside an Intel SGX enclave and examples have been setup for both Linux and Windows environments.

Intel ® SGX (Software Guard Extensions) can be thought of as a black-box where no other application running on the same device can see inside regardless of privilege. From a security standpoint this means that even if a malicious actor were to gain complete control of a system including root privileges, that actor, no matter what they tried, would not be able to access data inside of this “black-box”.

An Intel enclave is a form of user-level Trusted Execution Environment (TEE) which can provide both storage and execution. Meaning one can store sensitive information inside and also move sensitive portions of a program or an entire application inside.

While testing, wolfSSL has placed both individual functions and entire applications inside the enclave. One of the wolfSSL examples shows a client inside the enclave with the only entry/exit points being “start_client”, “read”, and “write”. The client is pre-programmed with a peer to connect with and specific functionality. When “start_client” is invoked it connects to the peer using SSL/TLS and executes the pre-programmed tasks where the only data entering and leaving the enclave is the info being sent to and received from the peer. Other examples show placing a single cryptographic operation inside the enclave, passing in plain-text data and receiving back encrypted data masking execution of the cryptographic operations.

If you are working with SGX and need FIPS validated crypto running in an enclave contact us at fips@wolfssl.com or support@wolfssl.com with any questions. We would love the opportunity to field your questions and hear about your project!

Resources:
https://software.intel.com/en-us/blogs/2016/12/20/overview-of-an-intel-software-guard-extensions-enclave-life-cycle

wolfSSL FAQ page

The wolfSSL FAQ page can be useful for information or general questions that need need answers immediately. It covers some of the most common questions that the support team receives, along with the support team's responses. It's a great resource for questions about wolfSSL, embedded TLS, and for solutions to problems getting started with wolfSSL.

To view this page for yourself, please follow this link here.

Here is a sample list of 5 questions that the FAQ page covers:

  1. How do I build wolfSSL on ... (*NIX, Windows, Embedded device) ?
  2. How do I manage the build configuration of wolfSSL?
  3. How much Flash/RAM does wolfSSL use?
  4. How do I extract a public key from a X.509 certificate?
  5. Is it possible to use no dynamic memory with wolfSSL and/or wolfCrypt?

Have a  question that isn't on the FAQ? Feel free to email us at support@wolfssl.com.