Documentation ¶
Overview ¶
Package recordlayer implements the TLS Record Layer https://tools.ietf.org/html/rfc5246#section-6
Index ¶
Constants ¶
const ( HeaderSize = 13 MaxSequenceNumber = 0x0000FFFFFFFFFFFF )
RecordLayer enums
Variables ¶
This section is empty.
Functions ¶
func UnpackDatagram ¶
UnpackDatagram extracts all RecordLayer messages from a single datagram. Note that as with TLS, multiple handshake messages may be placed in the same DTLS record, provided that there is room and that they are part of the same flight. Thus, there are two acceptable ways to pack two DTLS messages into the same datagram: in the same record or in separate records. https://tools.ietf.org/html/rfc6347#section-4.2.3
Types ¶
type Header ¶
type Header struct { ContentType protocol.ContentType ContentLen uint16 Version protocol.Version Epoch uint16 SequenceNumber uint64 // uint48 in spec }
Header implements a TLS RecordLayer header
type RecordLayer ¶
RecordLayer which handles all data transport. The record layer is assumed to sit directly on top of some reliable transport such as TCP. The record layer can carry four types of content:
1. Handshake messages—used for algorithm negotiation and key establishment. 2. ChangeCipherSpec messages—really part of the handshake but technically a separate kind of message. 3. Alert messages—used to signal that errors have occurred 4. Application layer data
The DTLS record layer is extremely similar to that of TLS 1.1. The only change is the inclusion of an explicit sequence number in the record. This sequence number allows the recipient to correctly verify the TLS MAC.
https://tools.ietf.org/html/rfc4347#section-4.1
func (*RecordLayer) Marshal ¶
func (r *RecordLayer) Marshal() ([]byte, error)
Marshal encodes the RecordLayer to binary
func (*RecordLayer) Unmarshal ¶
func (r *RecordLayer) Unmarshal(data []byte) error
Unmarshal populates the RecordLayer from binary