Home
last modified time | relevance | path

Searched refs:client (Results 1 – 23 of 23) sorted by relevance

/mbedtls-latest/tests/suites/
Dtest_suite_ecjpake.data10 ECJPAKE round one: client, valid
118 ECJPAKE round two client: valid
121 ECJPAKE round two client: trailing byte
124 ECJPAKE round two client: no data
127 ECJPAKE round two client: ECParams too short
130 ECJPAKE round two client: ECParams not named curve
133 ECJPAKE round two client: ECParams wrong curve
136 ECJPAKE round two client: no data after ECParams
139 ECJPAKE round two client: length of first point too small
142 ECJPAKE round two client: length of first point too big
[all …]
Dtest_suite_psa_crypto_pake.data3 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
7 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
11 …SA_PAKE_PRIMITIVE_TYPE_DH, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
15 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_K1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
19 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 128):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
23 …PSA_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_1:"client":"server":0:ERR_IN…
27 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
31 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
35 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
39 …A_PAKE_PRIMITIVE_TYPE_ECC, PSA_ECC_FAMILY_SECP_R1, 256):PSA_ALG_SHA_256:"client":"server":0:ERR_IN…
[all …]
Dtest_suite_psa_crypto_pake.function106 psa_pake_operation_t *client,
217 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
221 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
226 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
231 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
236 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
241 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
249 psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
261 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_KEY_SHARE,
270 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_ZK_PUBLIC,
[all …]
Dtest_suite_ssl.function287 * can send a single message from the client to the server.
297 mbedtls_test_mock_socket client;
313 mbedtls_test_mock_socket_init(&client);
324 TEST_ASSERT(0 == mbedtls_test_mock_socket_connect(&client, &server,
331 send_ret = send(&client, message + written, MSGLEN - written);
339 int blocking_ret = send(&client, message, 1);
374 mbedtls_test_mock_socket_close(&client);
394 mbedtls_test_mock_socket client;
412 mbedtls_test_mock_socket_init(&client);
425 TEST_ASSERT(0 == mbedtls_test_mock_socket_connect(&client, &server,
[all …]
Dtest_suite_psa_crypto_driver_wrappers.function18 psa_pake_operation_t *client,
109 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
115 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
122 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
129 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
136 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
143 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
151 /* Adjust for indirect client driver setup in first pake_output call. */
155 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_KEY_SHARE,
163 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_ZK_PUBLIC,
[all …]
Dtest_suite_ssl.data100 Test mbedtls_endpoint sanity for the client
107 TLS 1.2:Move client handshake to HELLO_REQUEST
111 TLS 1.2:Move client handshake to CLIENT_HELLO
115 TLS 1.2:Move client handshake to SERVER_HELLO
119 TLS 1.2:Move client handshake to SERVER_CERTIFICATE
123 TLS 1.2:Move client handshake to SERVER_KEY_EXCHANGE
127 TLS 1.2:Move client handshake to CERTIFICATE_REQUEST
131 TLS 1.2:Move client handshake to SERVER_HELLO_DONE
135 TLS 1.2:Move client handshake to CLIENT_CERTIFICATE
139 TLS 1.2:Move client handshake to CLIENT_KEY_EXCHANGE
[all …]
Dtest_suite_ecdh.function301 /* client read server params */
305 /* client writes its key share */
320 /* server reads client key share */
341 /* client computes shared secret */
Dtest_suite_psa_crypto.function684 psa_pake_operation_t *client,
778 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
787 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
797 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
807 status = psa_pake_input(client, PSA_PAKE_STEP_KEY_SHARE,
817 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PUBLIC,
827 status = psa_pake_input(client, PSA_PAKE_STEP_ZK_PROOF,
845 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_KEY_SHARE,
851 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_ZK_PUBLIC,
857 PSA_ASSERT(psa_pake_output(client, PSA_PAKE_STEP_ZK_PROOF,
[all …]
Dtest_suite_x509parse.data187 …client@example.com, serialNumber=7101012255, uniqueIdentifier=#030B0037313031303132323535\nissued …
/mbedtls-latest/tests/scripts/
Dgenerate_tls13_compat_tests.py478 def generate_compat_test(client=None, server=None, cipher=None, named_group=None, sig_alg=None): argument
483 client=client, server=server, cipher=cipher[4:], sig_alg=sig_alg, named_group=named_group)
489 client_object = CLIENT_CLASSES[client](ciphersuite=cipher,
506 def generate_hrr_compat_test(client=None, server=None, argument
513 client=client, server=server, c_named_group=client_named_group,
518 client_object = CLIENT_CLASSES[client](named_group=client_named_group,
603 for client, server, cipher, named_group, sig_alg in \
609 if server == 'mbedTLS' or client == 'mbedTLS':
610 yield generate_compat_test(client=client, server=server,
616 for client, server, client_named_group, server_named_group in \
[all …]
Dall.sh315 --gnutls-cli=<GnuTLS_cli_path> GnuTLS client executable to use for most tests.
/mbedtls-latest/tests/src/test_helpers/
Dssl_helpers.c2030 mbedtls_test_ssl_endpoint client, server; in mbedtls_test_ssl_perform_handshake() local
2047 mbedtls_platform_zeroize(&client, sizeof(client)); in mbedtls_test_ssl_perform_handshake()
2062 TEST_ASSERT(mbedtls_test_ssl_endpoint_init(&client, in mbedtls_test_ssl_perform_handshake()
2068 mbedtls_ssl_set_timer_cb(&client.ssl, &timer_client, in mbedtls_test_ssl_perform_handshake()
2073 TEST_ASSERT(mbedtls_test_ssl_endpoint_init(&client, in mbedtls_test_ssl_perform_handshake()
2080 set_ciphersuite(&client.conf, options->cipher, forced_ciphersuite); in mbedtls_test_ssl_perform_handshake()
2108 TEST_ASSERT(mbedtls_ssl_conf_max_frag_len(&(client.conf), in mbedtls_test_ssl_perform_handshake()
2118 &client.conf, options->psk_str->x, in mbedtls_test_ssl_perform_handshake()
2137 mbedtls_ssl_conf_renegotiation(&(client.conf), in mbedtls_test_ssl_perform_handshake()
2142 mbedtls_ssl_conf_legacy_renegotiation(&(client.conf), in mbedtls_test_ssl_perform_handshake()
[all …]
/mbedtls-latest/programs/
DREADME.md44 …), [`pkey/dh_server.c`](pkey/dh_server.c): secure channel demonstrators (client, server). This pai…
65 * [`ssl/dtls_client.c`](ssl/dtls_client.c): a simple DTLS client program, which sends one datagram …
67 …er.c): a simple DTLS server program, which expects one datagram from the client and writes one dat…
69 …ic SSL client, which sends a short string and disconnects. This is primarily intended as a benchma…
71 * [`ssl/ssl_client1.c`](ssl/ssl_client1.c): a simple HTTPS client that sends a fixed request and di…
73 ….c`](ssl/ssl_fork_server.c): a simple HTTPS server using one process per client to send a fixed re…
75 …`](ssl/ssl_mail_client.c): a simple SMTP-over-TLS or SMTP-STARTTLS client. This client sends an em…
77 …`](ssl/ssl_pthread_server.c): a simple HTTPS server using one thread per client to send a fixed re…
79 …_server.c): a simple HTTPS server that sends a fixed response. It serves a single client at a time.
85 * [`ssl/ssl_client2.c`](ssl/ssl_client2.c): an HTTPS client that sends a fixed request and displays…
[all …]
/mbedtls-latest/programs/fuzz/
DREADME.md42 * client : simulates a client against (fuzzed) server traffic
43 * server : simulates a server against (fuzzed) client traffic
53 * Run a dummy python script to output either client or server corpus file like `python dummy.py tes…
56 Here is an example of dummy.py for extracting payload from client to server (if we used `tcp.dstpor…
65 # determine client or server based on port
/mbedtls-latest/docs/architecture/
Dpsa-shared-memory.md32 * a client of the crypto service, which makes a RPC to the crypto service;
33 * in some scenarios, a client of the client, which makes a RPC to the crypto client which re-shares…
42 2. The client (or client's client) modifies the input.
45 … code reads the length again and uses it without validation. A malicious client can modify the len…
47 …n separately calculates the ciphertext and the MAC from the plaintext. A client sets the plaintext…
50 * If the authenticated encryption calculates the ciphertext before the client changes the output bu…
57 2. The client (or client's client) modifies the intermediate data.
60 …tion in place. (This is how `mbedtls_rsa_pkcs1_sign` works.) A malicious client may write badly fo…
62 …client: the key and the data to sign are under the attestation application's control, and the fina…
69 2. The client (or client's client) reads the intermediate data.
[all …]
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.
344 functions `mbedtls_ssl_tls13_handshake_{client,server}_step` are the top level
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
/mbedtls-latest/tests/
DDescriptions.txt15 version, both ways (client/server), using client authentication or not.
/mbedtls-latest/
DChangeLog24 * In a PSA-client-only build (i.e. MBEDTLS_PSA_CRYPTO_CLIENT &&
31 * By default, the handling of TLS 1.3 tickets by the Mbed TLS client is now
101 client, if the client-provided certificate does not have appropriate values
106 than TLS client authentication could be able to use it for TLS client
113 * Fix TLS 1.3 client build and runtime when support for session tickets is
161 * Fix TLS connection failure in applications using an Mbed TLS client in
340 malicious client could cause information disclosure or a denial of service.
363 client could put the TLS 1.3-only server in an infinite loop processing
366 - If the TLS 1.2 implementation was disabled at runtime, a TLS 1.2 client
416 * In TLS 1.3 clients, fix an interoperability problem due to the client
[all …]
/mbedtls-latest/docs/
Dtls13-early-data.md43 data sent during the first flight of client messages while the handshake is in
152 While establishing a TLS 1.3 connection with a client using a combination
D3.0-migration-guide.md672 These days clients are very unlikely to do that. If you have a client that
1007 change the preferred order of ciphersuites on the server to those used on the client,
Dpsa-transition.md662 …s are identical except when the library is configured for use in a multi-client cryptography servi…
1174 #### Translating a legacy ephemeral key agreement TLS client workflow
1176 …wing workflow for an ephemeral Diffie-Hellman key agreement in a TLS 1.2 client. The PSA version o…
/mbedtls-latest/docs/architecture/psa-migration/
Dpsa-limitations.md50 be suboptimal for security, as it is prohibitively hard for the client to
71 3. Variant of the precedent: only drop client-side support. Server-side is
78 client-side the only option is to offer named groups and break the handshake
Dmd-cipher-dispatch.md197 * `MBEDTLS_PSA_CRYPTO_CLIENT` is enabled, and the client has not yet activated the connection to th…