Lines Matching refs:handshake

24 \ This is the common T0 code for processing handshake messages (code that
47 \ of the handshake; and it is cleared whenever a renegotiation or a
61 \ The handshake processor needs to defer back to the caller ('co') only
64 \ -- Some handshake data is expected.
66 \ -- The handshake is finished, and application data may flow. There may
67 \    be some incoming handshake data (HelloRequest from the server). This
283 \   0x01   handshake data is available
285 \   0x04   some data other than handshake or change-cipher-spec is available
429 \ If the current record type is "handshake" then the read byte is also
452 \ If the current record type is "handshake" then the read bytes are
506 \ In general we only deal with handshake data here. Alerts are processed
508 \ its own handling code. So we need to check that the data is "handshake"
512 \ neither handshake or alert, then an error is triggered.
513 : wait-for-handshake ( -- )
527 \ Read one byte of handshake data. Block until that byte is available.
532 		drop wait-for-handshake
549 \ Read one byte of handshake data. This pushes an integer in the 0..255 range.
570 		wait-for-handshake
594 \ Write one byte of handshake data.
723 \ Read a handshake message header: type and length. These are returned
725 : read-handshake-header-core ( -- lim type )
728 \ Read a handshake message header: type and length. If the header is for
731 : read-handshake-header ( -- lim type )
733 		read-handshake-header-core dup 0= while
1096 	read-handshake-header 20 <> if ERR_UNEXPECTED fail then
1312 	read-handshake-header 11 = ifnot ERR_UNEXPECTED fail then
1343 	\ We must close the chain AND the handshake message.