| /mbedtls-latest/tests/suites/ |
| D | test_suite_lmots.data | 2 # This test uses a fixed message, and then generates a private key, signs the
7 # This test uses a fixed message, and then generates a private key, signs the
12 # This test uses a NULL zero-length message, and then generates a private key,
17 # This test uses data from https://github.com/pmvr/python-hsslms due to the
21 # This test uses the same OTS key as the LMS hsslms interop test 1 (leaf 0 of
42 # This test uses data from https://github.com/pmvr/python-hsslms due to the
46 # This test uses the same OTS key as the LMS hsslms interop test 2 (leaf 1 of
67 # This test uses data from https://github.com/pmvr/python-hsslms due to the
90 # This test uses the valid signature from hsslms interop test 1, and then
96 # This test uses the valid signature from hsslms interop test 1, and then
[all …]
|
| D | test_suite_lms.data | 2 # This test uses a fixed message, and then generates a private key, signs the
7 # This test uses a NULL zero-length message, and then generates a private key,
12 # This test uses data from https://github.com/russhousley/pyhsslms due to the
15 # uses leaf key 0, so must be the first signature generated by the key if the
39 # The signature uses leaf key 1, so must be the second signature generated by
52 # This test uses data from https://github.com/russhousley/pyhsslms due to the limited
55 # uses leaf key 2, so must be the third signature generated by the key if the
83 # This test uses data from https://github.com/cisco/hash-sigs due to the
87 # signature uses leaf key 0, so must be the first signature generated by the key
111 # This test uses data from https://github.com/cisco/hash-sigs due to the
[all …]
|
| D | test_suite_psa_crypto_entropy.data | 5 # implementation of the algorithm that uses randomization, whether it's
6 # because the algorithm is randomized or because our implementation uses
|
| D | test_suite_rsa.function | 744 /* This test uses an insecure RNG, suitable only for testing.
969 /* This test uses an insecure RNG, suitable only for testing.
980 /* This test uses an insecure RNG, suitable only for testing.
1171 /* This test uses an insecure RNG, suitable only for testing.
1356 /* This test uses an insecure RNG, suitable only for testing.
1367 /* This test uses an insecure RNG, suitable only for testing.
|
| D | test_suite_psa_crypto_init.function | 33 /* PSA crypto uses the HMAC_DRBG module. It reads from the entropy source twice:
40 /* PSA crypto uses the CTR_DRBG module. In some configurations, it needs
|
| D | test_suite_psa_crypto_slot_management.data | 129 # writing, this happens in builds where AES uses a PSA driver and the
130 # PSA RNG uses AES-CTR_DRBG through the PSA AES.
|
| D | test_suite_net.function | 127 /* mbedtls_net_recv_timeout() uses select() and fd_set in the same way. */
|
| D | test_suite_psa_crypto_entropy.function | 104 * or because the implementation uses blinding. */
|
| D | test_suite_pkwrite.function | 95 * uses "\n" for newlines in both Windows and Linux.
|
| D | test_suite_psa_crypto_se_driver_hal_mocks.function | 87 * 0, which file-based storage uses as a temporary file. */
|
| /mbedtls-latest/3rdparty/p256-m/p256-m/ |
| D | README.md | 41 - The API uses arrays of octets for all input and output.
56 - Testing also uses dynamic analysis: valgrind, ASan, MemSan, UBSan.
92 depends on the value of operands on cores of interest. Namely, it never uses
93 integer division, and for multiplication by default it only uses 16x16->32 bit
162 that the externally-provided RNG function uses at most 384 bytes of stack).
216 TinyCrypto also uses no heap, only the stack. Here's the RAM used by each
299 - TinyCrypt uses a specialised routine for reduction modulo the curve prime,
303 - TinyCrypt uses Co-Z Jacobian formulas for point operation, which should be
306 - p256-m uses bits of inline assembly for 64-bit multiplication on the
307 platforms used for benchmarking, while TinyCrypt uses only C (and the
[all …]
|
| /mbedtls-latest/programs/ |
| D | README.md | 26 …pt.c`](pkey/pk_decrypt.c): loads a PEM or DER public/private key file and uses the key to encrypt/…
28 …ify.c`](pkey/pk_verify.c): loads a PEM or DER private/public key file and uses the key to sign/ver…
34 …/rsa_decrypt.c`](pkey/rsa_decrypt.c): loads an RSA public/private key and uses it to encrypt/decry…
38 …ey/rsa_verify.c`](pkey/rsa_verify.c): loads an RSA private/public key and uses it to sign/verify a…
40 …erify_pss.c`](pkey/rsa_verify_pss.c): loads an RSA private/public key and uses it to sign/verify a…
|
| /mbedtls-latest/tests/src/ |
| D | helpers.c | 282 static void mbedtls_test_set_case_uses_negative_0_internal(unsigned uses) in mbedtls_test_set_case_uses_negative_0_internal() argument
287 mbedtls_test_info.case_uses_negative_0 = uses; in mbedtls_test_set_case_uses_negative_0_internal()
|
| /mbedtls-latest/docs/architecture/psa-migration/ |
| D | md-cipher-dispatch.md | 20 As a developer of an application that uses Mbed TLS's interfaces (including legacy crypto),
26 As a developer of library code that uses Mbed TLS to perform cryptographic operations,
35 I want to build Mbed TLS in a way that uses my hardware wherever relevant,
64 …`MBEDTLS_AES_C && MBEDTLS_CIPHER_MODE_CBC` for AES-CBC, etc. In code that uses the PSA interfaces,…
97 We can classify code that implements or uses cryptographic mechanisms into several groups:
103 * Code that always uses PSA for crypto: TLS 1.3 (except things common with 1.2), LMS.
195 * For ciphers, the keystore is not initialized yet, and Mbed TLS uses a custom implementation of PS…
330 Note that this applies to TLS 1.3 as well, as some uses of hashes and all uses of ciphers there are…
354 …ded by the standards due to its smaller block size) and CTR-DRBG directly uses the low-level API f…
357 - CTR-DRBG only uses AES (and there is no plan to extend it to other block ciphers at the moment), …
|
| D | strategy.md | 49 `psa_crypto_init()` before TLS/X.509 uses PSA functions. (This prevents us
147 layer; the MD layer uses a variant where it dispatches to PSA if a driver is
281 - Step 1 is achieved for the crypto library regarding hashes: everything uses
296 - for ECC, we have no internal uses of the top-level algorithms (ECDSA, ECDH,
393 Unfortunately that's unlikely to fully work. For example, the MD layer uses the
395 distinct operation types. Similarly, the Cipher layer uses the same context
|
| D | psa-legacy-bridges.md | 69 …gh-level legacy crypto modules (md, cipher, pk) and need to combine that with uses of the PSA APIs.
183 The pk module uses signature formats intended for X.509. The PSA module uses the simplest sensible …
186 * For ECDSA, PSA uses a fixed-size concatenation of (r,s), whereas X.509 and pk use an ASN.1 DER en…
|
| /mbedtls-latest/3rdparty/p256-m/ |
| D | README.md | 1 …ained 32-bit environments. Mbed TLS documentation for integrating drivers uses p256-m as an exampl…
|
| /mbedtls-latest/docs/ |
| D | driver-only-builds.md | 47 make sure you call `psa_crypto_init()` before any function that uses the
97 You need to call `psa_crypto_init()` before any crypto operation that uses
105 - for code that uses only the PSA Crypto API: `PSA_WANT_ALG_xxx` from
107 - for code that uses non-PSA crypto APIs: `MBEDTLS_MD_CAN_xxx` from
191 - for code that uses only the PSA Crypto API: `PSA_WANT_ECC_xxx` from
|
| D | psa-transition.md | 231 …ementations remain supported in Mbed TLS 3.x even if the application code uses the PSA API. Howeve…
233 …development/docs/psa-driver-example-and-guide.md). In an application that uses both the legacy int…
342 * The legacy API uses the same interface for authenticated and non-authenticated ciphers, while the…
343 * The legacy API uses the same functions for encryption and decryption, while the PSA API has separ…
530 * The legacy API uses the same interface for authenticated and non-authenticated ciphers, while the…
531 * The legacy API uses the same functions for encryption and decryption, while the PSA API has separ…
636 The PSA API uses its internal random generator to generate keys (`psa_generate_key`), nonces for en…
638 If your application mixes uses of the PSA crypto API and the mbedtls API and you need to pass an RN…
647 Unless explicitly configured otherwise, the PSA random generator uses the default entropy sources c…
709 The PSA API uses policies and algorithm parameters rather than key types to distinguish between RSA…
[all …]
|
| D | use-psa-crypto.md | 43 uses PSA crypto. The parts of the TLS 1.3 code that will use PSA Crypto or not
|
| /mbedtls-latest/ |
| D | SECURITY.md | 121 DES. The pure software implementation in Mbed TLS implementation uses lookup
|
| D | README.md | 237 We've included example programs for a lot of different features and uses in [`programs/`](programs/…
298 … option `MBEDTLS_USE_PSA_CRYPTO` in `mbedtls_config.h`. Note that TLS 1.3 uses PSA cryptography fo…
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-shared-memory.md | 45 …h of an embedded field) Later, the crypto code reads the length again and uses it without validati…
81 2. The client reads the early output and uses that to calculate the next part of the input.
242 * Write a small program that uses a PSA function which copies inputs or outputs.
455 1. Take 1-2 days to create a basic prototype of a test that uses the approach.
683 Then, we could write a test that uses this function with memory poisoning and ensure that it fails.…
|
| D | alternative-implementations.md | 47 … For example, if an alternative implementation of asymmetric cryptography uses a different represe…
|
| D | mbed-crypto-storage-specification.md | 4 This document specifies how Mbed TLS uses storage.
43 The code uses the following constant in an internal header (note that despite the name, this value …
|
