Searched refs:stage (Results 1 – 14 of 14) sorted by relevance
| /mbedtls-latest/docs/architecture/ |
| D | tls13-support.md | 377 * coordination stage: check if the state should be bypassed. This stage is
383 reading to not modify the SSL context as this stage may be repeated if the
386 * fetching stage: at this stage we are sure of the type of the handshake
388 a coordination stage involving the next record type reading, the next
393 * pre-processing stage: prepare the SSL context for the message parsing. This
394 stage is optional. Any processing that must be done before the parsing of the
396 partial parsing of the handshake message may append at that stage like in the
399 * parsing stage: parse the message and restrict as much as possible any
404 * post-processing stage: following the parsing, further update of the SSL
405 context to prepare for the next incoming and outgoing messages. This stage is
[all …]
|
| D | psa-crypto-implementation-structure.md | 117 Functions and macros that are not intended for standardization, or that are at a stage where the dr…
|
| /mbedtls-latest/library/ |
| D | psa_crypto.c | 8497 if (operation->stage != PSA_PAKE_OPERATION_STAGE_SETUP) {
8529 operation->stage = PSA_PAKE_OPERATION_STAGE_COLLECT_INPUTS;
8546 if (operation->stage != PSA_PAKE_OPERATION_STAGE_COLLECT_INPUTS) {
8592 if (operation->stage != PSA_PAKE_OPERATION_STAGE_COLLECT_INPUTS) {
8636 if (operation->stage != PSA_PAKE_OPERATION_STAGE_COLLECT_INPUTS) {
8678 if (operation->stage != PSA_PAKE_OPERATION_STAGE_COLLECT_INPUTS) {
8705 psa_jpake_computation_stage_t *stage) argument
8708 if (stage->round == PSA_JPAKE_FIRST) {
8711 if (stage->io_mode == PSA_JPAKE_OUTPUT) {
8712 is_x1 = (stage->outputs < 1);
[all …]
|
| /mbedtls-latest/tests/suites/ |
| D | test_suite_psa_crypto_pake.function | 69 * Inject an error on the specified buffer ONLY it this is the correct stage.
549 * - terminated successfully if this exact error was expected at this stage
551 * stage or a different error code was expected)
567 * 1 input parameter that is relevant in this case and it's the stage at which
|
| D | test_suite_psa_crypto_driver_wrappers.function | 3058 /* Collecting input stage (no driver entry points) */
3071 /* Computation stage (driver entry points) */
|
| D | test_suite_psa_crypto.function | 6855 * and that each successful stage completes some ops (this is not mandated by
7030 * and that each successful stage completes some ops (this is not mandated by
7251 * is zero and that each successful signing stage completes some ops (this is
7452 * and that each successful stage completes some ops (this is not mandated by
7618 * and that each successful stage completes some ops (this is not mandated by
|
| /mbedtls-latest/include/psa/ |
| D | crypto_extra.h | 1870 uint8_t MBEDTLS_PRIVATE(stage);
|
| /mbedtls-latest/docs/architecture/psa-migration/ |
| D | psa-legacy-bridges.md | 158 … generally expect people to activate `MBEDTLS_USE_PSA_CRYPTO` at an early stage of their migration…
170 … generally expect people to activate `MBEDTLS_USE_PSA_CRYPTO` at an early stage of their migration…
192 …, or at least the curve's size. Therefore we are not going to add a generic function at this stage.
|
| D | md-cipher-dispatch.md | 10 …ocument](strategy.html) and is intended as a refinement. However, at this stage, there may be cont…
80 It is not a goal at this stage to make more code directly call `psa_xxx` functions. Rather, the goa…
|
| D | strategy.md | 364 CI in the "Results analysis" stage, by running
|
| /mbedtls-latest/docs/architecture/testing/ |
| D | driver-interface-test-strategy.md | 69 * Check the consequence of errors detected at each stage (slot number allocation or validation, key…
|
| /mbedtls-latest/docs/architecture/psa-thread-safety/ |
| D | psa-thread-safety.md | 208 …ey does not exist in the key store (this check cannot be done before this stage), sets the slot's …
209 * `psa_fail_key_creation` - If there is a failure at any point in the key creation stage, this clea…
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 6 … stage. There is ongoing work to implement this interface in Mbed TLS, which is the reference impl…
607 …y point to be called. It is called when all inputs are collected and the computation stage starts.
|
| /mbedtls-latest/ |
| D | ChangeLog | 3354 MBEDTLS_PLATFORM_GMTIME_R_ALT. At this stage Mbed TLS is only able to
3564 functionality shared by multiple Mbed TLS modules. At this stage
|
