Lines Matching refs:handshake

23 receives a message on the next protocol from the client it does not know that the handshake
75     BAD_HANDSHAKE_CIPHER = 102;  // No suitable handshake ciphers were found
98 UKEY2 supports negotiation of the cryptographic primitives used in the handshake. Two primitives
113 handshake ciphersuite negotiation is (see ClientInit and ServerInit messages for full details):
116 … public key using the chosen cipher and sends its own list of supported handshake cipher suites so…
121 The UKEY2 handshake consists of three messages. First, the client sends a `ClientInit` message to
128 After the handshake, both client and server derive authentication strings, which may be shown to
129 users for visual comparison or sent over some other channel in order to authenticate the handshake.
155 …handshake cipher and a commitment which is a hash of the `ClientFinished` message that would be se…
207 1.  Check that `handshake_cipher` matches a handshake cipher that was sent in
212 the `ClientFinished` message, the Client considers the handshake complete.
227   optional bytes public_key = 1;  // public key matching selected handshake cipher
233 message) for the server-selected handshake cipher.
250 After parsing the `ClientFinished` message, the Server considers the handshake complete.
290 mechanism, we believe that this handshake is resistant to an active man-in-the-middle attacker.
297 Furthermore, both the authentication string and next secret depend on the full handshake
298 transcript -- a manipulation of any handshake message by an adversary would change both the
305  not hold in theory, we do believe the security of the handshake is maintained in practice.