AuroraMiddleware/mbedtls
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
1,762 Commits 1 Branch 0 Tags 61 MiB
C 77.5%
Shell 15%
Python 4.7%
Makefile 0.9%
Jinja 0.8%
Other 0.9%
956c9e063d
Go to file
Paul Bakker 956c9e063d Reduced the input / output overhead with 200+ bytes and covered corner 
case

The actual input / output buffer overhead is only 301 instead of 512.
This requires a proper check on the padding_idx to prevent out of bounds
reads.

Previously a remote party could potentially trigger an access error and
thus stop the application when sending a malicious packet having
MAX_CONTENT_LEN of data, 32 bytes of MAC and a decrypted padlen of .
This would result in reading from in_ctr + 13 + 32 + MAX_CONTENT_LEN - 1 - 1
for 256 bytes (including fake padding check). Or 13 + 32 bytes over the
buffer length.

We now reset padding_idx to 0, if it's clear that it will never be a
valid padding (padlen > msg_len || msg_len + padlen + 256 > buffer_len)
2013-12-30 15:00:51 +01:00
doxygen Prep for PolarSSL 1.3.2 2013-11-04 17:29:42 +01:00
include Reduced the input / output overhead with 200+ bytes and covered corner 2013-12-30 15:00:51 +01:00
library Reduced the input / output overhead with 200+ bytes and covered corner 2013-12-30 15:00:51 +01:00
programs Added version of the SSL pthread server example 2013-12-30 14:55:54 +01:00
scripts Fixed error.fmt to match active error.c code 2013-11-21 17:34:13 +01:00
tests Do not print error on missing kill target in compat.sh 2013-12-19 17:47:24 +01:00
visualc Add files for (upcoming) AES-NI support 2013-12-25 13:03:26 +01:00
.gitignore Added proper gitignores for Linux CMake use 2012-11-18 22:56:39 +01:00
ChangeLog Reduced the input / output overhead with 200+ bytes and covered corner 2013-12-30 15:00:51 +01:00
CMakeLists.txt Added -Werror to Check buildtype 2013-12-30 14:09:27 +01:00
DartConfiguration.tcl Add 'memcheck' (valgrind) target to CMake 2013-09-08 20:08:09 +02:00
LICENSE - Changed line endings and encodings to unix and utf-8 2011-01-05 14:48:42 +00:00
Makefile - Added uninstall target 2012-11-13 10:28:43 +00:00
README.rst Updated README with simple formatting 2013-06-28 10:39:28 +02:00

README.rst 

===================
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
----

We intentionally only use the absolute minimum of **Make** functionality, as we have discovered that a lot of **Make** features are not supported on all different implementations of Make on different platforms. As such, the Makefiles sometimes require some handwork or `export` statements in order to work for your platform.

In order to build the source using Make, just enter at the command line:

    make

In order to run the tests, enter:

    make check

Depending on your platform, you might run into some issues. Please check the Makefiles in *library/*, *programs/* and *tests/* for options to manually add or remove for specific platforms. You can also check `the PolarSSL Knowledge Base <https://polarssl.org/kb>`_ for articles on your platform or issue.

In case you find that you need to do something else as well, please let us know what, so we can add it to the KB.

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.

Example programs
================

We've included example programs for a lot of different features and uses in *programs/*. Most programs only focus on a single feature or usage scenario, so keep that in mind when copying parts of the code.

Tests
=====

PolarSSL includes a elaborate test suite in *tests/* that initially requires Perl to generate the tests files (e.g. *test_suite_mpi.c*). These files are generates from a **function file** (e.g. *suites/test_suite_mpi.function*) and a **data file** (e.g. *suites/test_suite_mpi.data*). The **function file** contains the template for each test function. The **data file** contains the test cases, specified as parameters that should be pushed into a template function.

Contributing
============

#. `Check for open issues <https://github.com/polarssl/polarssl/issues>`_ or
   `start a discussion <https://polarssl.org/discussions>`_ around a feature
   idea or a bug.
#. Fork the `PolarSSL repository on Github <https://github.com/polarssl/polarssl>`_
   to start making your changes.
#. Write a test which shows that the bug was fixed or that the feature works
   as expected.
#. Send a pull request and bug us until it gets merged and published. We will
   include your name in the ChangeLog :)