mirrors-yuzu-emu/mbedtls
1
0
Fork 0
mirror of https://github.com/yuzu-emu/mbedtls synced 2024-11-24 20:08:22 +00:00
Code Issues Projects Releases Packages Wiki Activity
mbedtls/yotta/data
History
Manuel Pégourié-Gonnard c5e0372056 Rm SHA-1 from the yotta configuration
2015-08-06 09:57:54 +02:00
..
example-authcrypt
example-benchmark
example-hashing
example-selftest Rm SHA-1 from the yotta configuration 2015-08-06 09:57:54 +02:00
example-tls-client
adjust-config.sh Rm SHA-1 from the yotta configuration 2015-08-06 09:57:54 +02:00
entropy_hardware_poll.c
module.json
README.md Document yotta in top-level README 2015-08-06 09:57:54 +02:00
target_config.h

README.md

mbed TLS

mbed TLS (formerly known as PolarSSL) makes it trivially easy for developers to include cryptographic and SSL/TLS capabilities in their (embedded) products, facilitating this functionality with a minimal coding footprint. It offers an SSL library with an intuitive API and readable source code.

The Beta release of mbed TLS is an integration of mbed TLS in mbed OS. It is a testing preview only and not suitable for deployment: there is currently no source of random numbers, meaning no security at all for (D)TLS communication and other protocols that rely on random numbers.

Sample programs

This release includes the following examples:

  1. TLS client: downloads a file from an HTTPS server (mbed.org) and looks for a specific string in that file.

  2. Self test: tests different mbed TLS base functionalities.

  3. Benchmark: tests the time required to perform TLS base crypto functions.

These examples are integrated as yotta tests so that they are build automatically when you build mbed TLS. You'll find other examples in the various tests/example-* directories.

Running TLS

Please follow the instructions in the TLS client sample. These include a list of prerequisites and an explanation of building mbed TLS with yotta.

Contributing

We graciously accept bugs and contributions from the community. There are some requirements we need to fulfil in order to be able to integrate contributions in the main code:

  • Simple bug fixes to existing code do not contain copyright themselves and we can integrate those without any issue. The same goes for trivial contributions.

  • For larger contributions, e.g. a new feature, the code possibly falls under copyright law. We then need your consent to share in the ownership of the copyright. We have a form for that, which we will mail to you in case you submit a contribution or pull request that we deem this necessary for.

To contribute, please:

  • Check for open issues or start a discussion around a feature idea or a bug.

  • Fork the mbed TLS repository on Github to start making your changes.

  • Write a test that 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 :)