/mbedtls-latest/programs/ssl/ |
D | ssl_client2.c | 779 size_t len, written, frags, retry_left; in main() local 2534 written = 0; in main() 2538 while ((ret = mbedtls_ssl_write(&ssl, buf + written, in main() 2539 len - written)) < 0) { in main() 2559 written += ret; in main() 2560 } while (written < len); in main() 2593 written = ret; in main() 2595 if (written < len) { in main() 2597 "was truncated to size %u", (unsigned) written); in main() 2601 buf[written] = '\0'; in main() [all …]
|
D | ssl_server2.c | 1511 int ret = 0, len, written, frags, exchanges_left; in main() local 3954 for (written = 0, frags = 0; written < len; written += ret, frags++) { in main() 3955 while ((ret = mbedtls_ssl_write(&ssl, buf + written, len - written)) in main() 4001 written = ret; in main() 4004 buf[written] = '\0'; in main() 4005 mbedtls_printf(" %d bytes written in %d fragments\n\n%s\n", written, frags, (char *) buf); in main()
|
/mbedtls-latest/tests/suites/ |
D | test_suite_psa_crypto_op_fail.misc.data | 2 # test_suite_psa_crypto_op_fail.generated.data. The manually written
|
D | test_suite_timing.function | 28 /* Check that a non-zero time was written back */
|
D | test_suite_ssl.function | 166 size_t i, j, written, read; 227 written = read = 0; 230 input + written, put[j])); 231 written += put_ret[j]; 235 TEST_ASSERT(read <= written); 299 size_t written, read; 329 written = read = 0; 331 send_ret = send(&client, message + written, MSGLEN - written); 335 written += send_ret; 396 size_t written[ROUNDS]; [all …]
|
D | test_suite_psa_crypto_memory.function | 16 * been written, in a way that will detect an error in offset. */
|
D | test_suite_psa_crypto_entropy.function | 243 /* The seed is written by nv_seed callback functions therefore the injection will fail */
|
D | test_suite_bignum_mod.function | 286 * manually-written test cases with expected_ret != 0. */ 489 * manually-written test cases with oret != 0. */
|
D | test_suite_pkparse.function | 333 /* output_key_len is updated with the real amount of data written to
|
D | test_suite_x509write.function | 599 // Check correct tag and time written
|
D | test_suite_pkparse.data | 1209 # Note: Montgomery keys are written in Little endian format. 1217 # Note: Montgomery keys are written in Little endian format.
|
/mbedtls-latest/ |
D | BRANCHES.md | 76 keys written under any Mbed TLS 3.x with x <= y). 78 Mbed TLS 3.x can also read keys written by Mbed TLS 2.25.0 through 2.28.x
|
D | LICENSE | 62 means any form of electronic, verbal, or written communication sent 339 your rights to work written entirely by you; rather, the intent is to 356 b) Accompany it with a written offer, valid for at least three 449 the limitation as if written in the body of this License. 544 `Gnomovision' (which makes passes at compilers) written by James Hacker.
|
D | CONTRIBUTING.md | 18 - The code should be written in a clean and readable style, and must follow [our coding standards](… 19 - The code should be written in a portable generic way, that will benefit the whole community, and …
|
/mbedtls-latest/docs/proposed/ |
D | psa-driver-wrappers-codegen-migration-guide.md | 37 Please refer to psa-driver-interface.md for information on how a driver schema can be written.
|
D | psa-driver-interface.md | 199 2. `size_t *key_buffer_length`: the length of the data written to the key buffer in bytes. 210 …r of type `size_t *` is provided to report the actual length of the data written in the buffer if … 408 …lue` or `p_key_buffer`) and if applicable the size of the value has been written to the applicable… 532 * On success, `*key_buffer_length` must contain the number of bytes written to `key_buffer`. 699 * `output` buffer where the output is to be written. 752 * `output` Buffer where the implicit key is to be written. 1008 …partial success), the number of bytes of random data that the driver has written to the `output` b… 1261 …ext respectively, and `*key_buffer_length` contains the length of the data written to `key_buffer`.
|
/mbedtls-latest/tests/src/test_helpers/ |
D | ssl_helpers.c | 955 int *written, in mbedtls_ssl_write_fragment() argument 965 ret = mbedtls_ssl_write(ssl, buf + *written, buf_len - *written); in mbedtls_ssl_write_fragment() 967 *written += ret; in mbedtls_ssl_write_fragment()
|
/mbedtls-latest/docs/architecture/testing/ |
D | test-framework.md | 35 …riptions](#unit-test-descriptions). In addition, the description must be written on the same line …
|
/mbedtls-latest/3rdparty/p256-m/p256-m/ |
D | README.md | 6 especially suited to constrained 32-bit environments. It's written in standard 16 some might even risk weakening security for more speed. p256-m was written 525 While p256-m is standard C99, it is written with constrained 32-bit platforms
|
/mbedtls-latest/docs/architecture/ |
D | psa-shared-memory.md | 323 …ffers only, since it allows us to detect when a poisoned buffer is read but not when it is written. 326 …py of random data with the original to ensure that the output buffer has not been written directly. 346 …e simpler to implement than using existing tests, since the tests can be written to take into acco… 354 * All of the tests are written already, potentially saving development time. 477 …written that exercise the drivers in the required way. Fortunately, the only interfaces that need …
|
D | psa-keystore-design.md | 57 * `FILLING` or `PENDING_DELETION` state: the slot is being written. 61 Note that a slot must not be moved in memory while it is being read or written.
|
D | alternative-implementations.md | 54 …nd then copy the context upwards through the call chain, or applications written in a language wit…
|
D | psa-storage-resilience.md | 17 _Committing_ means that when a function returns, the data has been written to the persistent storag… 30 …iously passed to `set()`. We do not try to handle the case where a file might be partially written. 482 …lly implemented: when this feature is enabled, the transaction file gets written during transactio…
|
D | tls13-support.md | 259 - When an TLS 1.3 structure is written or read by a function or as part of
|
/mbedtls-latest/tests/scripts/ |
D | all.sh | 302 --outcome-file=<path> File where test outcomes are written (not done if
|