Mbed TLS

From Glitchdata
Jump to navigation Jump to search

Template:Lowercase title Template:Multiple issues Template:Infobox software

mbed TLS (previously PolarSSL) is an implementation of the TLS and SSL protocols and the respective cryptographic algorithms and support code required. It is dual-licensed with the Apache License version 2.0 (with GPLv2 also available). Stated on the website is that mbed TLS aims to be "easy to understand, use, integrate and expand".


The PolarSSL SSL library is the official continuation fork of the XySSL SSL library. XySSL was created by the French "white hat hacker" Christophe Devine and was first released on November 1, 2006, under GPL and BSD licenses. In 2008, Christophe Devine was no longer able to support XySSL and allowed Paul Bakker to create the official fork, named PolarSSL.[1] In November 2014, PolarSSL was acquired by ARM Holdings.[2]

In 2011, the Dutch government approved an integration between OpenVPN and PolarSSL, which is named OpenVPN-NL. This version of OpenVPN has been approved for use in protecting government communications up to the level of Restricted.[3]

As of the release of version 1.3.10, PolarSSL has been rebranded to mbed TLS to better show its fit inside the mbed ecosystem.[4] It was also announced that the licence would change from GPL to Apache License later in 2015 (with a goal of before October).[5]


The core SSL library is written in the C programming language and implements the SSL module, the basic cryptographic functions and provides various utility functions. Unlike OpenSSL and other implementations of TLS, mbed TLS is designed to fit on small embedded devices, with the minimum complete TLS stack requiring under 60KB of program space and under 64 KB of RAM. It is also highly modular: each component, such as a cryptographic function, can be used independently from the rest of the framework. Versions are also available for Microsoft Windows and Linux. Because mbed TLS is written in the C programming language, without external dependencies, it works on most operating systems and architectures without any trouble.

Later versions of PolarSSL than 1.3.0, add abstraction layers for memory allocation and threading to the core "to support better integration with existing embedded operating systems".[6]

Design priorities

The mbed TLS library expresses a focus on readability of the code, documentation, automated regression tests, a loosely coupled design and portable code.[7]

Development documentation

The following documentation is available for developers:

  • High Level Design:[8] a high level description of the different modules inside the library, with UML diagrams, use cases and interactions in common scenarios.
  • API documentation:[9] Doxygen-generated documentation from the header files of the library.
  • Source code documentation:[10] The source code of the library is documented to clarify structures, decisions and code constructs.

Automated testing

mbed TLS provides automated testing of the code and of PolarSSL's compatibility as follows:

  • A test framework is included with the source code that contains over 5000 automated tests (based on the number of tests in version 1.3.2 of the library) to test for regressions and compatibility on different platforms.
  • A continuous integration system based on Buildbot[11]
  • A compatibility script (compat.sh[12]) that tests compatibility of SSL communication with OpenSSL.


mbed TLS is used as the SSL component in large open source projects:


mbed TLS is currently available for most Operating Systems including Linux, Microsoft Windows, OS X, OpenWrt, Android, iOS and FreeRTOS. Chipsets supported at least include ARM, x86, PowerPC, MIPS.


mbed TLS supports a number of different cryptographic algorithms:

AES, Camellia, DES, RC4, RC5, Triple DES, XTEA, Blowfish
Cryptographic hash functions
MD5, MD2, MD4, SHA-1, SHA-2
Public-key cryptography
RSA, Diffie-Hellman key exchange, Elliptic curve cryptography (ECC), Elliptic curve Diffie–Hellman (ECDH), Elliptic Curve DSA (ECDSA)

See also




External links

Template:Cryptographic software Template:TLS/SSL

  1. "About us". PolarSSL. https://polarssl.org/about-us. Retrieved 2014-05-08.
  2. "PolarSSL is now a part of ARM". 2014-11-24. https://polarssl.org/tech-updates/blog/polarssl-part-of-arm.
  3. [1] Template:Webarchive
  4. "mbed TLS 1.3.10 released". 2015-02-08. https://polarssl.org/tech-updates/releases/mbedtls-1.3.10-released. Retrieved 2015-02-09.
  5. "PolarSSL is dead, long live mbed TLS". ARM. http://community.arm.com/groups/internet-of-things/blog/2015/02/09/polarssl-is-dead-long-live-mbed-tls. Retrieved 2015-02-10.
  6. "New features in PolarSSL 1.3.0 – Tech Updates". Polarssl.org. https://polarssl.org/tech-updates/blog/new-features-in-polarssl-1.3.0. Retrieved 2014-05-08.
  7. "PolarSSL Features: easy to use SSL library and well-documented". Polarssl.org. https://polarssl.org/features. Retrieved 2014-05-08.
  8. "PolarSSL High Level Design". Polarssl.org. https://polarssl.org/high-level-design. Retrieved 2014-05-08.
  9. "v1.3.6 source code documentation – API Documentation". PolarSSL. https://polarssl.org/api. Retrieved 2014-05-08.
  10. "polarssl/polarssl — GitHub". Github.com. https://github.com/polarssl/polarssl. Retrieved 2014-05-08.
  11. "PolarSSL Core Features: Check out all technical details". Polarssl.org. https://polarssl.org/core-features. Retrieved 2014-05-08.
  12. executable file 1038 lines (940 sloc) 39.573 kb (2014-02-13). "polarssl/tests/compat.sh at development · polarssl/polarssl · GitHub". Github.com. https://github.com/polarssl/polarssl/blob/development/tests/compat.sh. Retrieved 2014-05-08.