Found 4 other functions taking a
tlsv1_record_layer
argument:
tlsv1_record_send - TLS record layer: Send a message @rl: Pointer to TLS record layer data @content_type: Content type (TLS_CONTENT_TYPE_*) @buf: Buffer for the generated TLS message (needs to have extra space for header, IV (TLS v1.1), and HMAC) @buf_size: Maximum buf size @payload: Payload to be sent @payload_len: Length of the payload @out_len: Buffer for returning the used buf length Returns: 0 on success, -1 on failure This function fills in the TLS record layer header, adds HMAC, and encrypts the data using the current write cipher.
tlsv1_record_change_write_cipher - TLS record layer: Change write cipher @rl: Pointer to TLS record layer data Returns: 0 on success (cipher changed), -1 on failure This function changes TLS record layer to use the new cipher suite configured with tlsv1_record_set_cipher_suite() for writing.
tlsv1_record_change_read_cipher - TLS record layer: Change read cipher @rl: Pointer to TLS record layer data Returns: 0 on success (cipher changed), -1 on failure This function changes TLS record layer to use the new cipher suite configured with tlsv1_record_set_cipher_suite() for reading.
tlsv1_record_receive - TLS record layer: Process a received message @rl: Pointer to TLS record layer data @in_data: Received data @in_len: Length of the received data @out_data: Buffer for output data (must be at least as long as in_data) @out_len: Set to maximum out_data length by caller; used to return the length of the used data @alert: Buffer for returning an alert value on failure Returns: Number of bytes used from in_data on success, 0 if record was not complete (more data needed), or -1 on failure This function decrypts the received message, verifies HMAC and TLS record layer header.