Lines Matching full:dtls
5 // DTLS implementation.
7 // NOTE: This is a not even a remotely production-quality DTLS
57 return 0, nil, fmt.Errorf("dtls: exceeded maximum packet length")
64 // A real DTLS implementation should be tolerant of errors,
68 return 0, nil, errors.New("dtls: failed to read record header")
75 return 0, nil, c.in.setErrorLocked(fmt.Errorf("dtls: received record with version %x when expecting version %x", vers, c.vers))
80 return 0, nil, c.in.setErrorLocked(fmt.Errorf("dtls: received record with version %x when expecting version %x", vers, expect))
91 return 0, nil, c.in.setErrorLocked(fmt.Errorf("dtls: bad epoch"))
95 return 0, nil, c.in.setErrorLocked(fmt.Errorf("dtls: bad sequence number"))
101 return 0, nil, c.in.setErrorLocked(fmt.Errorf("dtls: oversized record received with length %d", n))
142 // because OpenSSL's DTLS implementation will probably accept
205 // This is a test-only DTLS implementation, so there is no need to
306 // DTLS records include an explicit sequence number.
373 return nil, errors.New("dtls: bad handshake record")
382 return nil, errors.New("dtls: fragment length too long")
388 return nil, errors.New("dtls: bad handshake sequence number")
398 // without the DTLS bits.
401 return nil, errors.New("dtls: bad handshake length")
406 return nil, errors.New("dtls: bad fragment offset")
409 return nil, errors.New("dtls: bad fragment length")
419 // DTLSServer returns a new DTLS server side connection
429 // DTLSClient returns a new DTLS client side connection
