| /mbedtls-latest/docs/architecture/testing/ |
| 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 …
39 …pat.sh` has a description which succinctly describes for a human audience what the test does. The …
|
| 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, …
|
| 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-latest/library/ |
| D | aesni.h | 82 int mbedtls_aesni_has_support(unsigned int what);
84 #define mbedtls_aesni_has_support(what) 1
|
| D | aesni.c | 49 int mbedtls_aesni_has_support(unsigned int what) in mbedtls_aesni_has_support() argument
73 return (c & what) != 0; in mbedtls_aesni_has_support()
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-integration-guide.md | 37 <!-- TODO: what if the driver is provided as C source code? -->
39 <!-- TODO: what about additional include files? -->
|
| D | psa-driver-wrappers-codegen-migration-guide.md | 26 While that is the larger goal, for version 1.1 here's what's changed
|
| D | psa-driver-developer-guide.md | 26 …river description file declares which functions the driver implements and what cryptographic mecha…
|
| D | psa-conditional-inclusion-c.md | 94 Note: the implementation is always free to include support for more than what was explicitly reques…
235 If a mechanism should only be supported in an opaque driver, what does the core need to know about …
|
| /mbedtls-latest/tests/scripts/ |
| D | depends.py | 170 def announce(self, colors, what): argument
175 if what is True:
177 elif what is False:
|
| D | test_zeroize.gdb | 18 # problem is that a compiler would typically remove what it considers to be
|
| /mbedtls-latest/tests/suites/ |
| D | test_suite_mps.function | 61 /* Consume exactly what's available */
111 /* Consume exactly what's available */
236 * of the consumer exceeds what has been provided by the producer, and when
360 * - The consumer asks for more data than what's available.
389 /* Ask for more than what's available. */
484 * - The consumer has asked for more than what's available, so the
513 /* Ask for more than what's available. */
718 /* Ask for more than what's available. */
948 /* Check if output is in accordance with what was written */
988 * - The consumer asks for more data than what's available
|
| D | test_suite_psa_crypto_memory.function | 47 /* Note: We compare the first src_len bytes of each buffer, as this is what was copied. */
74 /* Note: We compare the first src_len bytes of each buffer, as this is what was copied. */
|
| D | test_suite_memory_buffer_alloc.function | 136 * bytes, and makes it hard to know what the reported size will be, so
|
| D | test_suite_asn1parse.function | 234 * valid depending on what the trailing garbage is. */
243 * we wouldn't know what to parse the input as.
|
| D | test_suite_psa_crypto_storage_format.function | 255 * can read back what this version wrote. */
|
| D | test_suite_psa_its.function | 4 * on top of stdio. It expects to know what the stdio name of a file is
|
| /mbedtls-latest/docs/architecture/psa-migration/ |
| D | psa-limitations.md | 178 It is unclear what parameters people use in practice. It looks like by default
190 algorithm identifiers (for SHA-256, SHA-384 and SHA-512), depending of what
317 There's no question about what to do with TLS (any version); the only question
|
| D | md-cipher-dispatch.md | 39 I want to build Mbed TLS without software that replicates what my hardware does,
255 …t have any implication on the RSA module. As far as `rsa.c` is concerned, what matters is that `PS…
265 …t's all there is, and it doesn't matter (from an API perspective) exactly what call chain leads to…
310 The existing interface in `md.h` is close to what we want, but not perfect. What's wrong with it?
358 … about getting random numbers - in fact PSA users don't even need to know what DRBG is used. In pa…
|
| D | strategy.md | 17 needs to be changed to use new APIs. For a more detailed account of what's
66 At the time of writing (early 2022) it is unclear what could be done about the
156 figure out what the future of that layer is: parts of it (parse/write, ECDSA
|
| D | psa-legacy-bridges.md | 174 * Wrapping, which is what `mbedtls_pk_setup_opaque` does. This works for any PSA key but is limited…
192 …arametrized by the algorithm. However, it is difficult to predict exactly what parameters are need…
276 * `mbedtls_pk_get_psa_attributes` sets the type and size based on what's in the pk context.
|
| /mbedtls-latest/ |
| D | LICENSE | 260 want its recipients to know that what they have is not the original, so
291 Whether that is true depends on what the Program does.
440 This section is intended to make thoroughly clear what is believed to
507 <one line to give the program's name and a brief idea of what it does.>
552 library. If this is what you want to do, use the GNU Lesser General
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-storage-resilience.md | 133 …er key. In this section, we explore recovery strategies, and we determine what the transaction lis…
161 …attributes: a key slot always exists, and it's up to the user to remember what, if anything, they …
283 …(i.e. doing it twice is the same as doing it once), we don't need to test what happens in executio…
297 Another benefit of this approach is that it is easier to specify and test what happens if the libra…
415 … in the internal storage. Note that this is done at a different time from what happens when creati…
506 …y manipulate. We instrument at least some of these tests to also indicate what operation is in pro…
|
| D | tls13-support.md | 252 - To mitigate what happened here
380 message. The latter occurs when it is not known what the next handshake message
|
| /mbedtls-latest/docs/ |
| D | use-psa-crypto.md | 20 X.509 and TLS. For example, enabling this option is what allows use of drivers
|
