Complete, compact and portable
Delivered in clear, readable, cross-platform and well documented C source code optimized for size and performance
Complete, compact and portable
Delivered in clear, readable, cross-platform and well documented C source code optimized for size and performance
TLS 1.3 protocol
Inside’s TLS Toolkit is quick to adopt latest IETF specifications
Robust security
TLS Toolkit is available with FIPS 140-2 validated Inside Secure Crypto Module
Inside Secure TLS Toolkit (formerly MatrixSSL) provides secure connectivity to devices with a small memory footprint. It has evolved to also serve networking devices requiring top performance. TLS Toolkit is a lean and efficient C source code SDK that is easy to integrate, and where bugs have few places to hide. TLS Toolkit is the SDK to replace RSA BSAFE or OpenSSL.
Thanks to a clear and well documented source code integration is faster and smoother than alternatives. To further simplify and accelerate the integration, Inside Secure offers developer level support.
Inside’s TLS Toolkit has always been quick to adopt the latest TLS specifications. For example, support for the TLS 1.3 protocol was released in August 2018, within days of IETF publishing the RFC 8446 specification.
Inside’s standard offering can be configured to a minimal code footprint of 66 kB (PSK). Manual optimization can further reduce the code footprint to meet the needs of memory constrained devices.
For applications that require FIPS validation, Inside’sTLS Toolkit is also offered with a state-of-the-art FIPS 140-2 validated crypto module (certificate #2389 https://csrc.nist.gov/projects/cryptographic-module-validation-program/Certificate/2389), successfully used in hundreds of millions devices.
For applications switching from OpenSSL a compatibility layer is provided to smoothen and accelerate migration to Inside’s TLS Toolkit.
TLS Toolkit is available under a dual-licensing model: GNU Public License and a Standard Commercial license. The dual license means that one can easily evaluate the library for free, but for commercial usage without the GPL constraints, one must acquire a license by contacting Inside Secure. The open source package can be downloaded from GitHub (https://github.com/matrixssl/matrixssl).
Commercial customers have access to our code under a commercial license (GPL-free) and benefit from a support contract with direct access to our development team. Their support requests are treated with priority. They will automatically receive new updates of the product.
Open source users can ask questions or propose patch through GitHub. They can also contact us by email: support@matrixssl.org.
As we are not able to contact open source users, please regularly check GitHub for the latest release.
We appreciate the work of security researchers that help us to maintain a high security standards. We would recommend that they report any security issues to support@matrixssl.org using the following PGP Key, Key fingerprint = D6AD F1C5 E34E 696B 0953 556C 8BB2 B39A 2795 C6B3.
This version fixes serious buffer handling vulnerabilities along with other smaller bugs. Upgrading to the latest version is highly recommended. Check the release notes on GitHub for details.
This version was driven by the need to update the test certificates that were expiring. There are no strong reasons to upgrade if you already use 3.9.0.
This version contains several new features and bug fixes. It is recommended for all users.
Full list of changes and changes in previous version are described in the source code package on GitHub:
https://github.com/matrixssl/matrixssl/releases/latest
For more detailled product information, download the documentation of the open source release below.
MatrixSSL EllipticCurveCiphers
The GPL version can be downloaded from: https://github.com/matrixssl/matrixssl/releases/latest