Home
last modified time | relevance | path

Searched refs:side (Results 1 – 25 of 26) sorted by relevance

12

/mbedtls-latest/library/
Decdh.c420 mbedtls_ecdh_side side) in ecdh_get_params_internal() argument
425 if (side == MBEDTLS_ECDH_THEIRS) { in ecdh_get_params_internal()
430 if (side != MBEDTLS_ECDH_OURS) { in ecdh_get_params_internal()
447 mbedtls_ecdh_side side) in mbedtls_ecdh_get_params() argument
450 if (side != MBEDTLS_ECDH_OURS && side != MBEDTLS_ECDH_THEIRS) { in mbedtls_ecdh_get_params()
470 return ecdh_get_params_internal(ctx, key, side); in mbedtls_ecdh_get_params()
476 mbedtls_everest_ecdh_side s = side == MBEDTLS_ECDH_OURS ? in mbedtls_ecdh_get_params()
485 key, side); in mbedtls_ecdh_get_params()
/mbedtls-latest/3rdparty/everest/library/
Deverest.c67 mbedtls_everest_ecdh_side side ) in mbedtls_everest_get_params() argument
70 mbedtls_x25519_ecdh_side s = side == MBEDTLS_EVEREST_ECDH_OURS ? in mbedtls_everest_get_params()
Dx25519.c105 mbedtls_x25519_ecdh_side side ) in mbedtls_x25519_get_params() argument
109 switch( side ) { in mbedtls_x25519_get_params()
/mbedtls-latest/docs/architecture/
Dtls13-support.md15 - Mbed TLS implements both the client and the server side of the TLS 1.3
81 - TLS 1.2 and TLS 1.3 with version negotiation on client and server side.
354 client side, the states related to certificate parsing and validation are
361 client side is a example of that.
381 will be, an example of that on client side being if we are going to receive a
432 outbound message on server side as well.
Dpsa-shared-memory.md111 …GlobalPlatform TEE Trusted Application (application running on the secure side of TrustZone on Cor…
198 …TLS, a [known issue](https://github.com/Mbed-TLS/mbedtls/issues/3266)). A side benefit of doing th…
/mbedtls-latest/
DSECURITY.md68 physical side channels as well. Remote and physical timing attacks are covered
75 #### Local non-timing side channels
83 side channel attacks. If local non-timing attacks are present in a use case or
DChangeLog360 * When negotiating TLS version on server side, do not fall back to the
461 * Fix a timing side channel in private key RSA operations. This side channel
511 the capabilities of the PSA side for either key.
547 * Add support for server-side TLS version negotiation. If both TLS 1.2 and
875 * Fix a potential heap buffer overread in TLS 1.3 client-side when
878 Arm, so that these systems are no longer vulnerable to timing side-channel
884 timing side-channel attacks. There is now an intrinsics-based AES-NI
895 calculation on the client side. It prevents a server with more accurate
1287 * Add support for client-side TLS version negotiation. If both TLS 1.2 and
1313 and hmac_demo.c, which use PSA and the md/cipher interfaces side
[all …]
/mbedtls-latest/3rdparty/everest/include/everest/
Dx25519.h121 mbedtls_x25519_ecdh_side side );
Deverest.h157 mbedtls_everest_ecdh_side side );
/mbedtls-latest/tests/
DDescriptions.txt16 For each ciphersuite/version/side/authmode it performs a full handshake
/mbedtls-latest/docs/architecture/psa-migration/
Dpsa-limitations.md71 3. Variant of the precedent: only drop client-side support. Server-side is
77 when moving to PSA. Server-side would work as above; unfortunately
78 client-side the only option is to offer named groups and break the handshake
Dtesting.md54 (We should have the same server-side.)
Dpsa-legacy-bridges.md141 …On the legacy side, this is an `mbedtls_pk_type_t` value and more. For ECDSA, the choice between r…
143 …On the PSA side, this is a `psa_key_type_t` value and an algorithm which is normally encoded as po…
Dmd-cipher-dispatch.md267 … the keystore, and plausibly a cipher accelerator might want entropy (for side channel countermeas…
/mbedtls-latest/include/mbedtls/
Decdh.h345 mbedtls_ecdh_side side);
/mbedtls-latest/tests/suites/
Dtest_suite_dhm.function145 /* The domain parameters must be the same on both side. */
Dtest_suite_ssl.function435 * of at least one byte on either side. */
3317 /* Client side, force SECP256R1 to make one key bitflip fail
3326 /* Server side */
4693 * initiate the handshake on server side before doing all the calls to
4742 * Now, check data on server side. It is not done in the previous loop as
4903 * can be sent from client side. Then send in a loop as much early data as
4937 * expansion) of early data on server side and the number of early data
Dtest_suite_ecp.function160 * but for the sake of simplicity only does half of each side. It's
/mbedtls-latest/docs/
Duse-psa-crypto.md134 is enabled, no change required on the application side.
Ddriver-only-builds.md128 `MBEDTLS_DETERMINISTIC_ECDSA` on the legacy side and
436 - AES is supported on the PSA side together with ECB mode, i.e.
Dpsa-transition.md258 The PSA API does not have an equivalent to the timing-side-channel-resistance utility functions in …
554 …ed value. Note that this comparison should be in constant time to avoid a side channel vulnerabili…
562 …ed value. Note that this comparison should be in constant time to avoid a side channel vulnerabili…
1151 …SA version of this workflow can also be used with other protocols, on the side of the party that s…
1176 …SA version of this workflow can also be used with other protocols, on the side of the party that r…
1201 * With either side, accessing the group: call [`psa_get_key_attributes`](https://mbed-tls.readthedo…
D3.0-migration-guide.md505 side-channel attacks.
/mbedtls-latest/programs/
DREADME.md89 In addition to providing options for testing client-side features, the `ssl_client2` program has op…
/mbedtls-latest/docs/architecture/psa-thread-safety/
Dpsa-thread-safety.md121 …ent-calling-conventions)), operations in progress can have memory related side effects. It is poss…
247 …`psa_get_and_lock_key_slot`. All other steps have no non resource-related side effects (except for…
/mbedtls-latest/docs/architecture/testing/
Dinvasive-testing.md69 …` function that does nothing (not a macro, to avoid accidentally skipping side effects in its para…

12