Repository: incubator-milagro-tls Updated Branches: refs/heads/master babfb4fd0 -> 74e45fc59
updated doxyfile to output code API Project: http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/commit/ff42067c Tree: http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/tree/ff42067c Diff: http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/diff/ff42067c Branch: refs/heads/master Commit: ff42067cf9ee41a84dd8a1197a3f24b541cbb824 Parents: babfb4f Author: Kealan McCusker <[email protected]> Authored: Mon May 16 20:26:19 2016 +0100 Committer: Kealan McCusker <[email protected]> Committed: Mon May 16 20:26:19 2016 +0100 ---------------------------------------------------------------------- Milagro.md | 44 ---------- README.md | 191 +++++++---------------------------------- doxygen/mbedtls.doxyfile | 11 +-- include/mbedtls/milagro.h | 22 ++--- mbedTLS.md | 173 +++++++++++++++++++++++++++++++++++++ 5 files changed, 219 insertions(+), 222 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/blob/ff42067c/Milagro.md ---------------------------------------------------------------------- diff --git a/Milagro.md b/Milagro.md deleted file mode 100644 index f073095..0000000 --- a/Milagro.md +++ /dev/null @@ -1,44 +0,0 @@ -<h2>README for mbed TLS with MILAGRO</h2> - -Milagro TLS has only been built and tested on Linux and Mac with the GCC tool chain. - -First install the mpin-crypto library and then the mbed TLS library. - -CMake is required to build the library and can usually be installed from -the operating system package manager. - -<ul type="disc"> - <li>sudo apt-get install cmake</li> -</ul> - -If not, then you can download it from www.cmake.org - - -<h2>Compiling mpin-crypto</h2> - -<ol type="disc"> - <li>git clone https://github.com/miracl/milagro-crypto</li> - <li>cd mpin-crypto</li> - <li>mkdir release</li> - <li>cd release</li> - <li>cmake -D CMAKE_INSTALL_PREFIX=/opt/amcl -D USE_ANONYMOUS=on -D WORD_LENGTH=64 -D BUILD_WCC=on -D BUILD_MPIN=on ..</li> - <li>make</li> - <li>make test</li> - <li>sudo make install</li> -</ol> - - -<h2>Compiling mbed TLS</h2> - -<ol type="disc"> - <li>git clone https://github.com/miracl/milagro-tls</li> - <li>cd mtls</li> - <li>mkdir release</li> - <li>cd release</li> - <li>cmake -D AMCL_INSTALL_DIR=/opt/amcl ..</li> - <li>make</li> - <li>make test</li> - <li>sudo make install</li> -</ol> - - http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/blob/ff42067c/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index 08c6289..018c4b5 100644 --- a/README.md +++ b/README.md @@ -1,173 +1,46 @@ -README for mbed TLS -=================== +<h2>README for mbed TLS with MILAGRO</h2> -Configuration -------------- +note: The original mbed TLS build instructions are in the file mbedTLS.md -mbed TLS should build out of the box on most systems. Some platform specific options are available in the fully-documented configuration file `include/mbedtls/config.h`, which is also the place where features can be selected. This file can be edited manually, or in a more programmatic way using the Perl script `scripts/config.pl` (use `--help` for usage instructions). +Milagro TLS has only been built and tested on Linux and Mac with the GCC tool chain. -Compiler options can be set using standard variables such as `CC` and `CFLAGS` when using the Make and CMake build system (see below). +First install the mpin-crypto library and then the mbed TLS library. -Compiling ---------- +CMake is required to build the library and can usually be installed from +the operating system package manager. -There are currently four active build systems within the mbed TLS releases: +<ul type="disc"> + <li>sudo apt-get install cmake</li> +</ul> -- yotta -- Make -- CMake -- Microsoft Visual Studio (Visual Studio 6 and Visual Studio 2010) +If not, then you can download it from www.cmake.org -The main systems used for development are CMake and yotta. Those systems are always complete and up-to-date. The others should reflect all changes present in the CMake and yotta build system, but some features are not ported there by default. -Please note that the yotta option is slightly different from the other build systems: +<h2>Compiling mpin-crypto</h2> -- a more minimalistic configuration file is used by default -- depending on the yotta target, features of mbed OS will be used in examples and tests +<ol type="disc"> + <li>git clone https://github.com/miracl/milagro-crypto</li> + <li>cd milagro-crypto</li> + <li>mkdir release</li> + <li>cd release</li> + <li>cmake -D CMAKE_INSTALL_PREFIX=/opt/amcl -D USE_ANONYMOUS=on -D WORD_LENGTH=64 -D BUILD_WCC=on -D BUILD_MPIN=on ..</li> + <li>make</li> + <li>make test</li> + <li>sudo make install</li> +</ol> -The Make and CMake build systems create three libraries: libmbedcrypto, libmbedx509, and libmbedtls. Note that libmbedtls depends on libmbedx509 and libmbedcrypto, and libmbedx509 depends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific order, for example the GNU linker wants `-lmbedtls -lmbedx509 -lmbedcrypto`. Also, when loading shared libraries using dlopen(), you'll need to load libmbedcrypto first, then libmbedx509, before you can load libmbedtls. -### Yotta +<h2>Compiling mbed TLS</h2> -[yotta](http://yottabuild.org) is a package manager and build system developed by mbed; it is the build system of mbed OS. To install it on your platform, please follow the yotta [installation instructions](http://docs.yottabuild.org/#installing). +<ol type="disc"> + <li>git clone https://github.com/miracl/milagro-tls</li> + <li>cd milagro-tls</li> + <li>mkdir release</li> + <li>cd release</li> + <li>cmake -D AMCL_INSTALL_DIR=/opt/amcl ..</li> + <li>make</li> + <li>make test</li> + <li>sudo make install</li> +</ol> -Once yotta is installed, you can use it to download the latest version of mbed TLS form the yotta registry with: - - yotta install mbedtls - -and build it with: - - yotta build - -If, on the other hand, you already have a copy of mbed TLS from a source other than the yotta registry, for example from cloning our GitHub repository, or from downloading a tarball of the standalone edition, then you'll need first need to generate the yotta module by running: - - yotta/create-module.sh - -from the mbed TLS root directory. This will create the yotta module in the `yotta/module` directory. You can then change to that directory and build as usual: - - cd yotta/module - yotta build - -In any case, you'll probably want to set the yotta target before building unless it's already set globally; for more information on using yotta, please consult the [yotta documentation](http://docs.yottabuild.org/). - -For more details on the yotta/mbed OS edition of mbed TLS, including example programs, please consult the [Readme at the root of the yotta module](https://github.com/ARMmbed/mbedtls/blob/development/yotta/data/README.md). - -### Make - -We intentionally only use the absolute minimum of `Make` functionality, as 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 - -The tests need Perl to be built and run. If you don't have Perl installed, you can skip building the tests with: - - make no_test - -You'll still be able to run a much smaller set of tests with: - - programs/test/selftest - -In order to build for a Windows platform, you should use `WINDOWS_BUILD=1` if the target is Windows but the build environment is Unix-like (for instance when cross-compiling, or compiling from an MSYS shell), and `WINDOWS=1` if the build environment is a Windows shell (for instance using mingw32-make) (in that case some targets will not be available). - -Setting the variable `SHARED` in your environment will build shared libraries in addition to the static libraries. Setting `DEBUG` gives you a debug build. You can override `CFLAGS` and `LDFLAGS` by setting them in your environment or on the make command line; if you do so, essential parts such as `-I` will still be preserved. Warning options may be overridden separately using `WARNING_CFLAGS`. - -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 mbed TLS Knowledge Base](https://tls.mbed.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 - -In order to run the tests, enter: - - make test - -The test suites need Perl to be built. If you don't have Perl installed, you'll want to disable the test suites with: - - cmake -DENABLE_TESTING=Off . - -If you disabled the test suites, but kept the programs enabled, you can still run a much smaller set of tests with: - - programs/test/selftest - -To configure CMake for building shared libraries, use: - - cmake -DUSE_SHARED_MBEDTLS_LIBRARY=On . - -There are many different build modes available within the CMake buildsystem. Most of them are available for gcc and clang, though some are compiler-specific: - -- 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. -- ASan. This instruments the code with AddressSanitizer to check for memory errors. (This includes LeakSanitizer, with recent version of gcc and clang.) (With recent version of clang, this mode also instruments the code with UndefinedSanitizer to check for undefined behaviour.) -- ASanDbg. Same as ASan but slower, with debug information and better stack traces. -- MemSan. This instruments the code with MemorySanitizer to check for uninitialised memory reads. Experimental, needs recent clang on Linux/x86\_64. -- MemSanDbg. Same as MemSan but slower, with debug information, better stack traces and origin tracking. -- Check. This activates the compiler warnings that depend on optimization and treats all warnings as errors. - -Switching build modes in CMake is simple. For debug mode, enter at the command line: - - cmake -D CMAKE_BUILD_TYPE=Debug . - -To list other available CMake options, use: - - cmake -LH - -Note that, with CMake, if you want to change the compiler or its options after you already ran CMake, you need to clear its cache first, e.g. (using GNU find): - - find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} + - CC=gcc CFLAGS='-fstack-protector-strong -Wa,--noexecstack' cmake . - -### Microsoft Visual Studio - -The build files for Microsoft Visual Studio are generated for Visual Studio 2010. - -The solution file `mbedTLS.sln` 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. However, the selftest program in `programs/test/` is still available. - -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 ------ - -mbed TLS includes an elaborate test suite in `tests/` that initially requires Perl to generate the tests files (e.g. `test\_suite\_mpi.c`). These files are generated 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 test functions. The `data file` contains the test cases, specified as parameters that will be passed to the test function. - -For machines with a Unix shell and OpenSSL (and optionally GnuTLS) installed, additional test scripts are available: - -- `tests/ssl-opt.sh` runs integration tests for various TLS options (renegotiation, resumption, etc.) and tests interoperability of these options with other implementations. -- `tests/compat.sh` tests interoperability of every ciphersuite with other implementations. -- `tests/scripts/test-ref-configs.pl` test builds in various reduced configurations. -- `tests/scripts/key-exchanges.pl` test builds in configurations with a single key exchange enabled -- `tests/scripts/all.sh` runs a combination of the above tests, plus some more, with various build options (such as ASan, full `config.h`, etc). - -Configurations --------------- - -We provide some non-standard configurations focused on specific use cases in the `configs/` directory. You can read more about those in `configs/README.txt` - -Contributing ------------- - -We gratefully accept bug reports and contributions from the community. There are some requirements we need to fulfill in order to be able to integrate contributions: - -- Simple bug fixes to existing code do not contain copyright themselves and we can integrate without issue. The same is true of trivial contributions. -- For larger contributions, such as a new feature, the code can possibly fall under copyright law. We then need your consent to share in the ownership of the copyright. We have a form for this, which we will send to you in case you submit a contribution or pull request that we deem this necessary for. - -### Process - -1. [Check for open issues](https://github.com/ARMmbed/mbedtls/issues) or [start a discussion](https://tls.mbed.org/discussions) around a feature idea or a bug. -2. Fork the [mbed TLS repository on GitHub](https://github.com/ARMmbed/mbedtls) to start making your changes. As a general rule, you should use the "development" branch as a basis. -3. Write a test which shows that the bug was fixed or that the feature works as expected. -4. Send a pull request and bug us until it gets merged and published. We will include your name in the ChangeLog :) http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/blob/ff42067c/doxygen/mbedtls.doxyfile ---------------------------------------------------------------------- diff --git a/doxygen/mbedtls.doxyfile b/doxygen/mbedtls.doxyfile index 6a00f47..68b586b 100644 --- a/doxygen/mbedtls.doxyfile +++ b/doxygen/mbedtls.doxyfile @@ -664,7 +664,8 @@ WARN_LOGFILE = # directories like "/usr/src/myproject". Separate the files or directories # with spaces. -INPUT = . +INPUT = . \ + ../include/mbedtls/ # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is @@ -883,7 +884,7 @@ GENERATE_HTML = YES # If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `html' will be used as the default path. -HTML_OUTPUT = . +HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for # each generated HTML page (for example: .htm,.php,.asp). If it is left blank @@ -1296,7 +1297,7 @@ EXTRA_SEARCH_MAPPINGS = # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will # generate Latex output. -GENERATE_LATEX = NO +GENERATE_LATEX = YES # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be @@ -1403,7 +1404,7 @@ LATEX_BIB_STYLE = plain # The RTF output is optimized for Word 97 and may not look very pretty with # other RTF readers or editors. -GENERATE_RTF = NO +GENERATE_RTF = YES # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be @@ -1473,7 +1474,7 @@ MAN_LINKS = NO # generate an XML file that captures the structure of # the code including all documentation. -GENERATE_XML = NO +GENERATE_XML = YES # The XML_OUTPUT tag is used to specify where the XML pages will be put. # If a relative path is entered the value of OUTPUT_DIRECTORY will be http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/blob/ff42067c/include/mbedtls/milagro.h ---------------------------------------------------------------------- diff --git a/include/mbedtls/milagro.h b/include/mbedtls/milagro.h index 74b2118..29e336e 100644 --- a/include/mbedtls/milagro.h +++ b/include/mbedtls/milagro.h @@ -1,5 +1,10 @@ -/* +/** + + \file milagro.h + + \brief Milagro defines and structures. Depends on milagro-crypto + Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,13 +21,6 @@ under the License. */ -/* - * milagro.h - * - * support for milagro_p2p and milagro_cs - * require an extern library: milagro-crypto - * - */ @@ -194,7 +192,7 @@ int mbedtls_ssl_milagro_cs_alloc_memory(int client_or_server, mbedtls_milagro_cs * \param milagro_cs milagro_cs struct which contains the parameters * to be initialized * - * \retun 0 if the parameters are good, -1 otherwise + * \return 0 if the parameters are good, -1 otherwise * */ int mbedtls_milagro_cs_check(int client_or_server, mbedtls_milagro_cs_context *milagro_cs ); @@ -219,7 +217,7 @@ int mbedtls_milagro_cs_read_client_parameters( mbedtls_milagro_cs_context *milag * \param milagro_cs milagro_cs struct in which the parameters has to be * stored * - * \retun 0 if the reading finish well, -1 otherwise + * \return 0 if the reading finish well, -1 otherwise * */ int mbedtls_milagro_cs_authenticate_client( mbedtls_milagro_cs_context *milagro_cs ); @@ -282,10 +280,6 @@ void mbedtls_milagro_cs_free( mbedtls_milagro_cs_context *milagro_cs); */ struct mbedtls_milagro_p2p_context { - /* - * See the paper TODO what paper? - * - */ int date; /*!< set to zero in case of not using time permit */ octet client_rec_key; /*!< Client's receiver key provided by the TA */ octet server_sen_key; /*!< Server's sender key provided by the TA */ http://git-wip-us.apache.org/repos/asf/incubator-milagro-tls/blob/ff42067c/mbedTLS.md ---------------------------------------------------------------------- diff --git a/mbedTLS.md b/mbedTLS.md new file mode 100644 index 0000000..08c6289 --- /dev/null +++ b/mbedTLS.md @@ -0,0 +1,173 @@ +README for mbed TLS +=================== + +Configuration +------------- + +mbed TLS should build out of the box on most systems. Some platform specific options are available in the fully-documented configuration file `include/mbedtls/config.h`, which is also the place where features can be selected. This file can be edited manually, or in a more programmatic way using the Perl script `scripts/config.pl` (use `--help` for usage instructions). + +Compiler options can be set using standard variables such as `CC` and `CFLAGS` when using the Make and CMake build system (see below). + +Compiling +--------- + +There are currently four active build systems within the mbed TLS releases: + +- yotta +- Make +- CMake +- Microsoft Visual Studio (Visual Studio 6 and Visual Studio 2010) + +The main systems used for development are CMake and yotta. Those systems are always complete and up-to-date. The others should reflect all changes present in the CMake and yotta build system, but some features are not ported there by default. + +Please note that the yotta option is slightly different from the other build systems: + +- a more minimalistic configuration file is used by default +- depending on the yotta target, features of mbed OS will be used in examples and tests + +The Make and CMake build systems create three libraries: libmbedcrypto, libmbedx509, and libmbedtls. Note that libmbedtls depends on libmbedx509 and libmbedcrypto, and libmbedx509 depends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific order, for example the GNU linker wants `-lmbedtls -lmbedx509 -lmbedcrypto`. Also, when loading shared libraries using dlopen(), you'll need to load libmbedcrypto first, then libmbedx509, before you can load libmbedtls. + +### Yotta + +[yotta](http://yottabuild.org) is a package manager and build system developed by mbed; it is the build system of mbed OS. To install it on your platform, please follow the yotta [installation instructions](http://docs.yottabuild.org/#installing). + +Once yotta is installed, you can use it to download the latest version of mbed TLS form the yotta registry with: + + yotta install mbedtls + +and build it with: + + yotta build + +If, on the other hand, you already have a copy of mbed TLS from a source other than the yotta registry, for example from cloning our GitHub repository, or from downloading a tarball of the standalone edition, then you'll need first need to generate the yotta module by running: + + yotta/create-module.sh + +from the mbed TLS root directory. This will create the yotta module in the `yotta/module` directory. You can then change to that directory and build as usual: + + cd yotta/module + yotta build + +In any case, you'll probably want to set the yotta target before building unless it's already set globally; for more information on using yotta, please consult the [yotta documentation](http://docs.yottabuild.org/). + +For more details on the yotta/mbed OS edition of mbed TLS, including example programs, please consult the [Readme at the root of the yotta module](https://github.com/ARMmbed/mbedtls/blob/development/yotta/data/README.md). + +### Make + +We intentionally only use the absolute minimum of `Make` functionality, as 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 + +The tests need Perl to be built and run. If you don't have Perl installed, you can skip building the tests with: + + make no_test + +You'll still be able to run a much smaller set of tests with: + + programs/test/selftest + +In order to build for a Windows platform, you should use `WINDOWS_BUILD=1` if the target is Windows but the build environment is Unix-like (for instance when cross-compiling, or compiling from an MSYS shell), and `WINDOWS=1` if the build environment is a Windows shell (for instance using mingw32-make) (in that case some targets will not be available). + +Setting the variable `SHARED` in your environment will build shared libraries in addition to the static libraries. Setting `DEBUG` gives you a debug build. You can override `CFLAGS` and `LDFLAGS` by setting them in your environment or on the make command line; if you do so, essential parts such as `-I` will still be preserved. Warning options may be overridden separately using `WARNING_CFLAGS`. + +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 mbed TLS Knowledge Base](https://tls.mbed.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 + +In order to run the tests, enter: + + make test + +The test suites need Perl to be built. If you don't have Perl installed, you'll want to disable the test suites with: + + cmake -DENABLE_TESTING=Off . + +If you disabled the test suites, but kept the programs enabled, you can still run a much smaller set of tests with: + + programs/test/selftest + +To configure CMake for building shared libraries, use: + + cmake -DUSE_SHARED_MBEDTLS_LIBRARY=On . + +There are many different build modes available within the CMake buildsystem. Most of them are available for gcc and clang, though some are compiler-specific: + +- 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. +- ASan. This instruments the code with AddressSanitizer to check for memory errors. (This includes LeakSanitizer, with recent version of gcc and clang.) (With recent version of clang, this mode also instruments the code with UndefinedSanitizer to check for undefined behaviour.) +- ASanDbg. Same as ASan but slower, with debug information and better stack traces. +- MemSan. This instruments the code with MemorySanitizer to check for uninitialised memory reads. Experimental, needs recent clang on Linux/x86\_64. +- MemSanDbg. Same as MemSan but slower, with debug information, better stack traces and origin tracking. +- Check. This activates the compiler warnings that depend on optimization and treats all warnings as errors. + +Switching build modes in CMake is simple. For debug mode, enter at the command line: + + cmake -D CMAKE_BUILD_TYPE=Debug . + +To list other available CMake options, use: + + cmake -LH + +Note that, with CMake, if you want to change the compiler or its options after you already ran CMake, you need to clear its cache first, e.g. (using GNU find): + + find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} + + CC=gcc CFLAGS='-fstack-protector-strong -Wa,--noexecstack' cmake . + +### Microsoft Visual Studio + +The build files for Microsoft Visual Studio are generated for Visual Studio 2010. + +The solution file `mbedTLS.sln` 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. However, the selftest program in `programs/test/` is still available. + +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 +----- + +mbed TLS includes an elaborate test suite in `tests/` that initially requires Perl to generate the tests files (e.g. `test\_suite\_mpi.c`). These files are generated 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 test functions. The `data file` contains the test cases, specified as parameters that will be passed to the test function. + +For machines with a Unix shell and OpenSSL (and optionally GnuTLS) installed, additional test scripts are available: + +- `tests/ssl-opt.sh` runs integration tests for various TLS options (renegotiation, resumption, etc.) and tests interoperability of these options with other implementations. +- `tests/compat.sh` tests interoperability of every ciphersuite with other implementations. +- `tests/scripts/test-ref-configs.pl` test builds in various reduced configurations. +- `tests/scripts/key-exchanges.pl` test builds in configurations with a single key exchange enabled +- `tests/scripts/all.sh` runs a combination of the above tests, plus some more, with various build options (such as ASan, full `config.h`, etc). + +Configurations +-------------- + +We provide some non-standard configurations focused on specific use cases in the `configs/` directory. You can read more about those in `configs/README.txt` + +Contributing +------------ + +We gratefully accept bug reports and contributions from the community. There are some requirements we need to fulfill in order to be able to integrate contributions: + +- Simple bug fixes to existing code do not contain copyright themselves and we can integrate without issue. The same is true of trivial contributions. +- For larger contributions, such as a new feature, the code can possibly fall under copyright law. We then need your consent to share in the ownership of the copyright. We have a form for this, which we will send to you in case you submit a contribution or pull request that we deem this necessary for. + +### Process + +1. [Check for open issues](https://github.com/ARMmbed/mbedtls/issues) or [start a discussion](https://tls.mbed.org/discussions) around a feature idea or a bug. +2. Fork the [mbed TLS repository on GitHub](https://github.com/ARMmbed/mbedtls) to start making your changes. As a general rule, you should use the "development" branch as a basis. +3. Write a test which shows that the bug was fixed or that the feature works as expected. +4. Send a pull request and bug us until it gets merged and published. We will include your name in the ChangeLog :) +
