| /mbedtls-development/library/ |
| A D | aesni.c | 48 int mbedtls_aesni_has_support( unsigned int what ) in mbedtls_aesni_has_support() argument
63 return( ( c & what ) != 0 ); in mbedtls_aesni_has_support()
|
| A D | aesni.h | 58 int mbedtls_aesni_has_support( unsigned int what );
|
| /mbedtls-development/docs/proposed/ |
| A D | psa-driver-integration-guide.md | 43 <!-- TODO: what if the driver is provided as C source code? -->
45 <!-- TODO: what about additional include files? -->
|
| A D | psa-driver-developer-guide.md | 25 …river description file declares which functions the driver implements and what cryptographic mecha…
|
| A D | psa-driver-interface.md | 47 …river description file declares which functions the driver implements and what cryptographic mecha…
377 … its components. TODO: what sanity checks? Value ranges (e.g. p < n), sanity checks such as parity…
378 …liptic curve private keys (`PSA_KEY_TYPE_ECC_KEY_PAIR`), check the size and range. TODO: what else?
379 …PE_ECC_PUBLIC_KEY`), check the size and range, and that the point is on the curve. TODO: what else?
527 …he driver must mix the whole supplied entropy, even if there is more than what the driver requires…
861 * Bits 0–7 are a _persistence level_. This value indicates what device management actions can cause…
906 … but there is no obligation for them to declare functions. The core knows what the function names …
|
| A D | psa-conditional-inclusion-c.md | 226 If a mechanism should only be supported in an opaque driver, what does the core need to know about …
|
| /mbedtls-development/docs/architecture/testing/ |
| A D | test-framework.md | 13 Each test case has a description which succinctly describes for a human audience what the test does…
20 …Rationale: 66 characters is what our various tools assume (leaving room for 14 more characters on …
33 …opt.sh` has a description which succinctly describes for a human audience what the test does. The …
|
| A D | psa-storage-format-testing.md | 27 If the test passes with version V, this means that the test data is consistent with what the implem…
29 … on version W with the same data that proves that version W can read back what version V wrote. Fr…
85 …ally based on an enumeration of available constants and some knowledge of what attributes (sizes, …
|
| A D | invasive-testing.md | 9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o…
20 This document currently focuses on data structure manipulation and storage, which is what the crypt…
42 > * on top of stdio. It expects to know what the stdio name of a file is
214 | Correctness | ! Difficult to ensure that what we test is what we run |
254 * Writing reliable debugger scripts is hard. We need to have confidence that we're testing what we …
|
| /mbedtls-development/.github/ |
| A D | pull_request_template.md | 21 If there is any API change, what's the incentive and logic for it.
|
| /mbedtls-development/tests/suites/ |
| A D | test_suite_mps.function | 59 /* Consume exactly what's available */
104 /* Consume exactly what's available */
218 * of the consumer exceeds what has been provided by the producer, and when
335 * - The consumer asks for more data than what's available.
362 /* Ask for more than what's available. */
457 * - The consumer has asked for more than what's available, so the
484 /* Ask for more than what's available. */
685 /* Ask for more than what's available. */
932 /* Check if output is in accordance with what was written */
976 * - The consumer asks for more data than what's available
|
| A D | test_suite_memory_buffer_alloc.function | 144 * bytes, and makes it hard to know what the reported size will be, so
|
| A D | test_suite_psa_crypto_storage_format.function | 184 * can read back what this version wrote. */
|
| A D | test_suite_psa_its.function | 4 * on top of stdio. It expects to know what the stdio name of a file is
|
| A D | test_suite_asn1parse.function | 241 * valid depending on what the trailing garbage is. */
250 * we wouldn't know what to parse the input as.
|
| A D | test_suite_entropy.function | 477 // Determine what should have happened with manual entropy internal logic
|
| A D | test_suite_pkcs1_v15.function | 238 /* Check that the output in invalid cases is what the default
|
| A D | test_suite_pk.function | 219 * is expected because that's what the library has done forever.
|
| A D | test_suite_psa_crypto.function | 310 * to set lengths, and in what order with
5078 /* Verify that the signature is what is expected. */
5636 /* We don't know what ciphertext length to expect, but check that
|
| A D | test_suite_ssl.function | 374 * caller knows what portion of the message can be dropped.
|
| /mbedtls-development/tests/scripts/ |
| A D | test_zeroize.gdb | 30 # problem is that a compiler would typically remove what it considers to be
|
| /mbedtls-development/ |
| A D | README.md | 105 In case you find that you need to do something else as well, please let us know what, so we can add…
249 - [What external dependencies does Mbed TLS rely on?](https://tls.mbed.org/kb/development/what-ex…
|
| /mbedtls-development/docs/architecture/ |
| A D | tls13-experimental.md | 322 - To mitigate what happened here
|
| /mbedtls-development/docs/ |
| A D | 3.0-migration-guide.md | 9 two questions: (1) am I affected? (2) if yes, what's my migration path?
541 they don't recognize, and this is what Mbed TLS does by default. This option
|
| /mbedtls-development/doxygen/ |
| A D | mbedtls.doxyfile | 1341 # standard header. Notice: only use this tag if you know what you are doing!
1348 # standard footer. Notice: only use this tag if you know what you are doing!
1551 # if you want to understand what is going on.
|