Rivoreo Source Code Repositories
src.rivoreo.one / security / mbedtls / ceb7b1209c52ff875fe8754030bc09a0d97ac360 / . / programs
tree: 0c113a6fd777427b620ef961384fe5035db5083d [path history] [download]
  1. .gitignore
  2. CMakeLists.txt
  3. Makefile
  4. README.md
  5. aes/
  6. hash/
  7. pkey/
  8. random/
  9. ssl/
  10. test/
  11. util/
  12. wince_main.c
  13. x509/
programs/README.md

Mbed TLS sample programs

This subdirectory mostly contains sample programs that illustrate specific features of the library, as well as a few test and support programs.

Symmetric cryptography (AES) examples

  • aes/aescrypt2.c: file encryption and authentication, demonstrating the low-level AES interface and HMAC.
    Warning: this program illustrates how to roll your own block cipher mode. Most applications should not do this and should instead use the standard library functions (e.g. mbedtls_aes_crypt_cbc).

  • aes/crypt_and_hash.c: file encryption and authentication, demonstrating the generic cipher interface and the generic hash interface.

Hash (digest) examples

Public-key cryptography examples

Generic public-key cryptography (pk) examples

  • pkey/gen_key.c: generate a key for any of the supported public-key algorithms (RSA or ECC) and write it to a file that can be used by the other pk sample programs.

  • pkey/key_app.c: Load a PEM or DER public key or private key file and dump its content.

  • pkey/key_app_writer.c: Load a PEM or DER public key or private key file and write it to a new PEM or DER file.

  • pkey/pk_encrypt.c, pkey/pk_decrypt.c: Load a PEM or DER public/private key file and use the key to encrypt/decrypt a short string through the generic public-key interface.

  • pkey/pk_sign.c, pkey/pk_verify.c: Load a PEM or DER private/public key file and use the key to sign/verify a short string.

ECDSA and RSA signature examples

Diffie-Hellman key exchange examples

  • pkey/dh_client.c, pkey/dh_server.c: secure channel demonstrator (client, server). Illustrates how to set up a secure channel using RSA for authentication and Diffie-Hellman to set up a shared AES session key.

  • pkey/ecdh_curve25519.c: demonstration of a elliptic curve Diffie-Hellman (ECDH) key agreement.

Bignum (mpi) usage examples

Random number generator (RNG) examples

  • random/gen_entropy.c: illustrates using the default entropy sources to generate random data.
    Note: most applications should use the entropy generator only to seed a cryptographic pseudorandom generator, as illustrated by random/gen_random_ctr_drbg.c.

  • random/gen_random_ctr_drbg.c: illustrates using the default entropy sources to seed a pseudorandom generator, and using the resulting random generator to generate random data.

  • random/gen_random_havege.c: illustrates the HAVEGE entropy collector.

SSL/TLS examples

SSL/TLS sample applications

  • ssl/dtls_client.c: a simple DTLS client program which sends one datagram to the server and reads one datagram in response.

  • ssl/dtls_server.c: a simple DTLS server program which expects one datagram from the client and writes one datagram in response. This program supports DTLS cookies for hello verification.

  • ssl/mini_client.c: a minimalistic SSL client which sends a short string and disconnects. This is intended more as a benchmark; for a better example of a typical TLS client, see ssl/ssl_client1.c.

  • ssl/ssl_client1.c: a simple HTTPS client that sends a fixed request and displays the response.

  • ssl/ssl_fork_server.c: a simple HTTPS server using one process per client to send a fixed response. This program requires a Unix/POSIX environment implementing the fork system call.

  • ssl/ssl_mail_client.c: a simple SMTP-over-TLS or SMTP-STARTTLS client. This client sends an email with a fixed content.

  • ssl/ssl_pthread_server.c: a simple HTTPS server using one thread per client to send a fixed response. This program requires a the pthread library.

  • ssl/ssl_server.c: a simple HTTPS server that sends a fixed response. This server serves a single client at a time.

SSL/TLS feature demonstrators

Note: unlike most of the other programs under the programs/ directory, these two programs are not intended as a basis to start writing an application. They combine most of the features supported by the library, and most applications require only a few features. It is recommended to start with ssl_client1.c or ssl_server.c, and to look inside ssl/ssl_client2.c or ssl/ssl_server2.c to see how to use the specific features that your application needs.

  • ssl/ssl_client2.c: an HTTPS client that sends a fixed request and displays the response, with options to select TLS protocol features and Mbed TLS library features.

  • ssl/ssl_server2.c: an HTTPS server that sends a fixed response, with options to select TLS protocol features and Mbed TLS library features.

These programs have options to trigger certain behaviors (e.g. reconnection, renegotiation) so the ssl_server2 program can be useful to test features in your TLS client and the ssl_client2 program can be useful to test features in your TLS server.

Test utilities

  • test/benchmark.c: benchmark for cryptographic algorithms.

  • test/selftest.c: runs the self-test functions in all the library modules.

  • test/ssl_cert_test.c: verify some X.509 certificates, and verify that each certificate matches the corresponding private key (supported for RSA keys only).

  • test/udp_proxy.c: a UDP proxy that can inject certain failures (delay, duplicate, drop). Useful to test DTLS.

Development utilities

  • util/pem2der.c: a PEM to DER converter. Mbed TLS can read PEM files directly, but this utility can be useful to interact with other tools or with minimal Mbed TLS builds that lack PEM support.

  • util/strerror.c: print the error description corresponding to an integer status returned by an Mbed TLS function.

X.509 certificate examples