Home
last modified time | relevance | path

Searched refs:DTLS (Results 1 – 10 of 10) sorted by relevance

/net-tools-latest/mbedtls-2.4.0/tests/suites/
Dtest_suite_ssl.data1 SSL DTLS replay: initial state, seqnum 0
4 SSL DTLS replay: 0 seen, 1 arriving
7 SSL DTLS replay: 0 seen, 0 replayed
10 SSL DTLS replay: 0-1 seen, 2 arriving
13 SSL DTLS replay: 0-1 seen, 1 replayed
16 SSL DTLS replay: 0-1 seen, 0 replayed
19 SSL DTLS replay: new
22 SSL DTLS replay: way new
25 SSL DTLS replay: delayed
28 SSL DTLS replay: lastest replayed
[all …]
/net-tools-latest/libcoap/
DTODO17 -> DTLS functionality
18 -> Adding DTLS functions based on openssl
DCONTRIBUTE218 example some DTLS implementations and proxy functionality.
/net-tools-latest/mbedtls-2.4.0/yotta/data/
DREADME.md27 ## Performing TLS and DTLS connections
29 …DTLS connections with mbed TLS in mbed OS is provided in a separate yotta module: [mbed-tls-socket…
77 …ets](https://github.com/ARMmbed/mbed-tls-sockets). See "Performing TLS and DTLS connections" above.
/net-tools-latest/
DREADME.legacy163 which waits DTLS data sent by dtls-client application that
214 If you want to use DTLS then run client like this
217 For non-DTLS case, run client like this
DREADME.md214 ## Using DTLS link with echo-* programs
216 For DTLS client functionality, you can do this
225 For DTLS server functionality, you can do this
DREADME NAT.md69 # Also any TLS/DTLS traffic needs proper seed or random generator,
/net-tools-latest/tinydtls-0.8.2/
Dtinydtls.h.in1 /* tinydtls -- a very basic DTLS implementation
/net-tools-latest/mbedtls-2.4.0/tests/
Dssl-opt.sh273 if [ "$DTLS" -eq 1 ]; then
327 DTLS=1
329 DTLS=0
/net-tools-latest/mbedtls-2.4.0/
DChangeLog59 ssl_parse_hello_verify_request() for DTLS. Found by Guido Vranken.
153 with some peers over unreliable links. Avoid dropping an entire DTLS
331 * Support for DTLS 1.0 and 1.2 (RFC 6347).
498 * DTLS no longer hard-depends on TIMING_C, but uses a callback interface