Lines Matching +full:use +full:- +full:handshake

24 libssl and will make use of 3 integration points to inject faults. 2 of these
25 integration points will use new callbacks added to libssl. The final integration
29 -----------------------
31 ### TLS Handshake
34 handshake data (i.e. the contents of CRYPTO frames). However such faults may
35 need to be done in handshake messages that would normally be encrypted.
36 Additionally the contents of handshake messages are hashed and each peer
38 "Finished" message exchange - so any modifications would be rejected and the
39 handshake would fail.
45 modified by a "man-in-the-middle".
48 that enables modification of handshake data prior to it being encrypted and
71 called after each handshake message has been constructed and is ready to send, but
72 before it has been passed through the handshake hashing code. It will be passed
73 a pointer to the constructed handshake message in `msgin` along with its
74 associated length in `inlen`. The mutator will construct a replacement handshake
86 ### QUIC Pre-Encryption Packets
143 itself as a man-in-the-middle between the client and server. A BIO_s_dgram_pair()
158 ------------------
167 - An EncryptedExtensions handshake message being sent
168 - An ACK frame being sent
169 - A Datagram being sent
173 be provided with the parsed contents of that message in an easy to use
178 This is because, in MVP, it will be the client side that is under test - so the
226  * Run the TLS handshake to create a QUIC connection between the client and
250  * Enable tests to listen for pre-encryption QUIC packets being sent
281  * The general handshake message listener is sent the entire handshake message
282  * data block, including the handshake header itself
295  * to resize the handshake message (either to add new data to it, or to truncate
296  * it). newlen must include the length of the handshake message header. The
297  * handshake message buffer is over allocated, so this just changes the logical
307  * pre-parsed ack data that can be modified as required.
311  * Handshake message specific listeners. Unlike the general handshake message
312  * listener these messages are pre-parsed and supplied with message specific
313  * data and exclude the handshake header.
324 /* TODO(QUIC TESTING): Add listeners for other types of handshake message here */
329  * is the new length of the specific message excluding the handshake message
354  * Enable tests to listen for post-encryption QUIC packets being sent
392 -------------
412      * to use for testing purposes - but we just use the highest possible
495 parameters in the TLS handshake:
508                                           ee->extensions, &ee->extensionslen))