mirror of
https://github.com/Mbed-TLS/mbedtls.git
synced 2025-01-25 09:35:19 +00:00
Paul Bakker
00b2860e8d
pem_read_buffer() already update use_len after header and footer are read
After header and footer are read, pem_read_buffer() is able to determine the length of input data used. This allows calling functions to skip this PEM bit if an error occurs during its parsing. (cherry picked from commit 9255e8300e550b548b54603c77585921f442e391)
README for PolarSSL -- COMPILING There are currently three active build systems within the PolarSSL releases: - Make - CMake - Microsoft Visual Studio The main system used for development is CMake. That system is always the most up-to-date. The others should reflect all changes present in the CMake build system, but some features are not ported there by default. --- Make In order to build the source using Make, just enter at the command line: make In order to run the tests, enter: make check --- CMake In order to build the source using CMake, just enter at the command line: cmake . make There are 3 different active build modes specified within the CMake buildsystem: - Release This generates the default code without any unnecessary information in the binary files. - Debug This generates debug information and disables optimization of the code. - Coverage This generates code coverage information in addition to debug information. Switching build modes in CMake is simple. For debug mode, enter at the command line: cmake -D CMAKE_BUILD_TYPE:String="Debug" . In order to run the tests, enter: make test --- Microsoft Visual Studio The build files for Microsoft Visual Studio are generated for Visual Studio 6.0 all future Visual Studio's should be able to open and use this older version of the build files. The workspace 'polarssl.dsw' contains all the basic projects needed to build the library and all the programs. The files in tests are not generated and compiled, as these need a perl environment as well.
Description
An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
Readme
Multiple Licenses
199 MiB
Languages
C
72%
Shell
20.4%
Python
3.7%
Perl
1.6%
Makefile
1.1%
Other
1.1%