| /freebsd/crypto/openssl/test/ssl-tests/ |
| H A D | 26-tls13_client_auth.cnf | 11 test-6 = 6-client-auth-TLSv1.3-request-post-handshake
12 test-7 = 7-client-auth-TLSv1.3-require-fail-post-handshake
13 test-8 = 8-client-auth-TLSv1.3-require-post-handshake
14 test-9 = 9-client-auth-TLSv1.3-require-non-empty-names-post-handshake
15 test-10 = 10-client-auth-TLSv1.3-noroot-post-handshake
16 test-11 = 11-client-auth-TLSv1.3-request-force-client-post-handshake
17 test-12 = 12-client-auth-TLSv1.3-request-force-server-post-handshake
18 test-13 = 13-client-auth-TLSv1.3-request-force-both-post-handshake
210 [6-client-auth-TLSv1.3-request-post-handshake]
211 ssl_conf = 6-client-auth-TLSv1.3-request-post-handshake-ssl
[all …]
|
| /freebsd/crypto/openssl/test/recipes/ |
| H A D | 70-test_sslmessages.t | 174 #Test 1: Check we get all the right messages for a default handshake
182 "Default handshake test");
184 #Test 2: Resumption handshake
191 "Resumption handshake test");
198 #Test 3: A status_request handshake (client request only)
205 "status_request handshake test (client)");
207 #Test 4: A status_request handshake (server support only)
215 "status_request handshake test (server)");
217 #Test 5: A status_request handshake (client and server)
227 "status_request handshake test");
[all …]
|
| H A D | 70-test_tls13messages.t | 205 #Test 1: Check we get all the right messages for a default handshake
214 "Default handshake test");
216 #Test 2: Resumption handshake
224 "Resumption handshake test");
229 #Test 3: A status_request handshake (client request only)
236 "status_request handshake test (client)");
238 #Test 4: A status_request handshake (server support only)
245 "status_request handshake test (server)");
247 #Test 5: A status_request handshake (client and server)
257 "status_request handshake test");
[all …]
|
| H A D | 70-test_sslsessiontick.t | 50 # NewSessionTicket message seen; Full handshake
56 #Test 2: If the server does not accept tickets we should get a normal handshake
59 # NewSessionTicket message not seen; Full handshake
66 #Test 3: If the client does not accept tickets we should get a normal handshake
69 # NewSessionTicket message not seen; Full handshake
77 # NewSessionTicket message not seen; Abbreviated handshake
91 # NewSessionTicket message seen; Abbreviated handshake
106 # NewSessionTicket message seen; Full handshake.
125 # NewSessionTicket message seen; Abbreviated handshake.
132 # NewSessionTicket message not seen; Abbreviated handshake.
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_tlsext_servername_callback.pod | 47 handshake will be aborted. The value of the alert to be used should be stored in
54 However, the handshake will continue and send a warning alert instead. The value
72 handshake. In TLSv1.2 the servername is only negotiated on initial handshakes
77 =item On the client, before the handshake
83 session from the original handshake had a servername accepted by the server then
88 =item On the client, during or after the handshake and a TLSv1.2 (or below)
91 If the session from the original handshake had a servername accepted by the
97 =item On the client, during or after the handshake and a TLSv1.2 (or below)
103 =item On the server, before the handshake
105 The function will always return NULL before the handshake
[all …]
|
| H A D | SSL_connect.pod | 5 SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
15 SSL_connect() initiates the TLS/SSL handshake with a server. The communication
24 handshake has been finished or an error occurred.
28 to continue the handshake, indicating the problem by the return value -1.
41 impacts after a successful TLSv1.3 handshake or a successful TLSv1.2 (or below)
42 resumption handshake, because the last peer to communicate in the handshake is
45 been received for the final handshake message.
61 The TLS/SSL handshake was not successful but was shut down controlled and
67 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
72 The TLS/SSL handshake was not successful, because a fatal error occurred either
|
| H A D | SSL_do_handshake.pod | 5 SSL_do_handshake - perform a TLS/SSL handshake
15 SSL_do_handshake() will wait for a SSL/TLS handshake to take place. If the
16 connection is in client mode, the handshake will be started. The handshake
26 once the handshake has been finished or an error occurred.
30 to continue the handshake. In this case a call to SSL_get_error() with the
47 The TLS/SSL handshake was not successful but was shut down controlled and
53 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
58 The TLS/SSL handshake was not successful because a fatal error occurred either
|
| H A D | SSL_CTX_set_verify.pod | 52 This makes the handshake suspend and return control to the calling application
59 Note that the handshake may still be aborted if a subsequent invocation of the
69 Post-Handshake Authentication extension to be added to the ClientHello such that
70 post-handshake authentication can be requested by the server. If B<val> is 0
93 certificate verification process can be checked after the TLS/SSL handshake
95 The handshake will be continued regardless of the verification result.
101 fails, the TLS/SSL handshake is
109 fails, the TLS/SSL handshake is
117 handshake is immediately terminated with a "handshake failur
[all...] |
| H A D | SSL_in_init.pod | 11 - retrieve information about the handshake state machine
29 awaiting handshake messages, or 0 otherwise.
31 SSL_in_before() returns 1 if no SSL/TLS handshake has yet been initiated, or 0
48 SSL_get_state() returns a value indicating the current state of the handshake
62 B<message> is the name of a handshake message that is being or has been sent, or
72 No handshake messages have yet been been sent or received.
76 Handshake message sending/processing has completed.
93 SSL_get_state() returns the current handshake state.
|
| H A D | SSL_CTX_set_ct_validation_callback.pod | 41 TLS handshake with the verification mode set to B<SSL_VERIFY_PEER>, if the peer
42 presents no valid SCTs the handshake will be aborted.
43 If the verification mode is B<SSL_VERIFY_NONE>, the handshake will continue
49 handshake completion, even after session resumption since the verification
54 handshake continues, and the verification status is not modified, regardless of
57 handshake completion.
59 the handshake.
61 handshake completion, such delayed SCT checks should only be performed when the
69 The TLS handshake is aborted if the verification mode is not B<SSL_VERIFY_NONE>
82 In that case the handshake continues as it would had no callback been
|
| H A D | SSL_key_update.pod | 34 SSL_key_update() must only be called after the initial handshake has been
51 handshake over an existing SSL/TLS connection. The next time an IO operation
56 handshake.
60 session associated with the current connection in the new handshake.
64 for a new handshake to be sent to the client. The next time an IO operation is
67 handshake and it may or may not attempt to resume an existing session. If
68 a new handshake is started then this will be handled transparently by calling
74 new handshake. For historical reasons, DTLS clients will not attempt to resume
75 the session in the new handshake.
|
| H A D | SSL_accept.pod | 5 SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake
15 SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake.
24 handshake has been finished or an error occurred.
28 to continue the handshake, indicating the problem by the return value -1.
46 The TLS/SSL handshake was not successful but was shut down controlled and
52 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
57 The TLS/SSL handshake was not successful because a fatal error occurred either
|
| H A D | SSL_CTX_set_num_tickets.pod | 26 the client after a full handshake. Set the desired value (which could be 0) in
28 the start of the handshake.
35 Tickets are also issued on receipt of a post-handshake certificate from the
40 was used for the initial handshake. If the initial handshake was a full
41 handshake then SSL_set_num_tickets() can be called again prior to calling
48 sent in this manner after the initial handshake has completed, and only for
|
| H A D | SSL_CTX_set_cert_cb.pod | 26 been set. A zero is returned on error which will abort the handshake with a
27 fatal internal error alert. A negative return value will suspend the handshake
28 and the handshake function will return immediately.
30 indicate, that the handshake was suspended. The next call to the handshake
50 A more advanced callback might examine the handshake parameters and set
|
| /freebsd/share/man/man4/ |
| H A D | lp.4 | 110 data plus one handshake).
112 different choice of which line to use as handshake.
123 Handshake out.
135 Handshake in.
140 sender writes the 4 most significant bits and raises the handshake line;
141 receiver reads the 4 bits and raises its handshake to acknowledge;
143 the handshake; receiver reads the data and lowers its handshake.
152 to be transmitted) without changing the state of the handshake.
154 Note that the end-of-packet marker assumes that the handshake signal and
172 Handshake out.
[all …]
|
| H A D | wg.4 | 74 This is used in their handshake to guard against future compromise of the
99 .It Handshake
100 Two peers handshake to mutually authenticate each other and to
102 Either peer may initiate a handshake.
106 Due to the handshake behavior, there is no connected or disconnected
171 .It "Handshake for peer X did not complete after 5 seconds, retrying"
182 .It "Invalid handshake initiation"
183 The incoming handshake packet could not be processed.
187 The incoming handshake initiation packet had an invalid MAC.
189 for the handshake receive
[all...] |
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_set_tlsext_servername_callback.3 | 178 handshake will be aborted. The value of the alert to be used should be stored in
184 However, the handshake will continue and send a warning alert instead. The value
199 handshake. In TLSv1.2 the servername is only negotiated on initial handshakes
201 .IP "On the client, before the handshake" 4
202 .IX Item "On the client, before the handshake"
207 session from the original handshake had a servername accepted by the server then
211 .IP "On the client, during or after the handshake and a TLSv1.2 (or below) resumption occurred" 4
212 .IX Item "On the client, during or after the handshake and a TLSv1.2 (or below) resumption occurred"
213 If the session from the original handshake had a servername accepted by the
218 .IP "On the client, during or after the handshake and a TLSv1.2 (or below) resumption did not occur…
[all …]
|
| H A D | SSL_CTX_set_verify.3 | 187 This makes the handshake suspend and return control to the calling application
194 Note that the handshake may still be aborted if a subsequent invocation of the
204 Post-Handshake Authentication extension to be added to the ClientHello such that
205 post-handshake authentication can be requested by the server. If \fBval\fR is 0
224 certificate verification process can be checked after the \s-1TLS/SSL\s0 handshake
226 The handshake will be continued regardless of the verification result.
231 fails, the \s-1TLS/SSL\s0 handshake is
239 fails, the \s-1TLS/SSL\s0 handshake is
246 handshake is immediately terminated with a \*(L"handshake failure\*(R" alert.
255 during the initial handshake. This flag must be used together with
[all …]
|
| H A D | SSL_connect.3 | 140 SSL_connect \- initiate the TLS/SSL handshake with an TLS/SSL server
150 \&\fBSSL_connect()\fR initiates the \s-1TLS/SSL\s0 handshake with a server. The communication
158 handshake has been finished or an error occurred.
162 to continue the handshake, indicating the problem by the return value \-1.
175 impacts after a successful TLSv1.3 handshake or a successful TLSv1.2 (or below)
176 resumption handshake, because the last peer to communicate in the handshake is
179 been received for the final handshake message.
190 The \s-1TLS/SSL\s0 handshake was not successful but was shut down controlled and
195 The \s-1TLS/SSL\s0 handshake was successfully completed, a \s-1TLS/SSL\s0 connection has been
199 The \s-1TLS/SSL\s0 handshake was not successful, because a fatal error occurred either
|
| H A D | SSL_do_handshake.3 | 140 SSL_do_handshake \- perform a TLS/SSL handshake
150 \&\fBSSL_do_handshake()\fR will wait for a \s-1SSL/TLS\s0 handshake to take place. If the
151 connection is in client mode, the handshake will be started. The handshake
160 once the handshake has been finished or an error occurred.
164 to continue the handshake. In this case a call to \fBSSL_get_error()\fR with the
176 The \s-1TLS/SSL\s0 handshake was not successful but was shut down controlled and
181 The \s-1TLS/SSL\s0 handshake was successfully completed, a \s-1TLS/SSL\s0 connection has been
185 The \s-1TLS/SSL\s0 handshake was not successful because a fatal error occurred either
|
| H A D | SSL_CTX_set_ct_validation_callback.3 | 176 \&\s-1TLS\s0 handshake with the verification mode set to \fB\s-1SSL_VERIFY_PEER\s0\fR, if the peer
177 presents no valid SCTs the handshake will be aborted.
178 If the verification mode is \fB\s-1SSL_VERIFY_NONE\s0\fR, the handshake will continue
184 handshake completion, even after session resumption since the verification
189 handshake continues, and the verification status is not modified, regardless of
192 handshake completion.
194 the handshake.
196 handshake completion, such delayed \s-1SCT\s0 checks should only be performed when the
204 The \s-1TLS\s0 handshake is aborted if the verification mode is not \fB\s-1SSL_VERIFY_NONE\s0\fR
217 In that case the handshake continues as it would had no callback been
|
| H A D | SSL_key_update.3 | 169 \&\fBSSL_key_update()\fR must only be called after the initial handshake has been
186 handshake over an existing \s-1SSL/TLS\s0 connection. The next time an \s-1IO\s0 operation
191 handshake.
195 session associated with the current connection in the new handshake.
199 for a new handshake to be sent to the client. The next time an \s-1IO\s0 operation is
202 handshake and it may or may not attempt to resume an existing session. If
203 a new handshake is started then this will be handled transparently by calling
209 new handshake. For historical reasons, \s-1DTLS\s0 clients will not attempt to resume
210 the session in the new handshake.
|
| H A D | SSL_in_init.3 | 146 \&\- retrieve information about the handshake state machine
164 awaiting handshake messages, or 0 otherwise.
166 \&\fBSSL_in_before()\fR returns 1 if no \s-1SSL/TLS\s0 handshake has yet been initiated, or 0
183 \&\fBSSL_get_state()\fR returns a value indicating the current state of the handshake
197 \&\fBmessage\fR is the name of a handshake message that is being or has been sent, or
204 No handshake messages have yet been been sent or received.
207 Handshake message sending/processing has completed.
219 \&\fBSSL_get_state()\fR returns the current handshake state.
|
| /freebsd/crypto/openssl/test/ |
| H A D | README.ssltest.md | 38 * HandshakeMode - which handshake flavour to test:
39 - Simple - plain handshake (default)
44 When HandshakeMode is Resume or Renegotiate, the original handshake is expected
46 handshake.
55 both client and server. Lowering the fragment size will split handshake and
63 * ExpectedResult - expected handshake outcome. One of
64 - Success - handshake success
65 - ServerFail - serverside handshake failure
66 - ClientFail - clientside handshake failure
90 - Yes - resumed handshake
[all …]
|
| /freebsd/crypto/openssl/test/helpers/ |
| H A D | ssl_test_ctx.h | 21 /* Couldn't test resumption/renegotiation: original handshake failed. */
148 /* Whether to test a resumed/renegotiated handshake. */
161 * Extra server/client configurations. Per-handshake.
163 /* First handshake. */
165 /* Resumed handshake. */
169 * Test expectations. These apply to the LAST handshake.
198 /* Whether the second handshake is resumed or a full handshake (boolean). */
|