From cd61faccc85805a000ce405adbb8d7739d2a1c25 Mon Sep 17 00:00:00 2001 From: Nikos Mavrogiannopoulos Date: Sun, 24 Aug 2014 09:55:42 +0200 Subject: updated manual --- manual/html_node/DTLS-sessions.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'manual/html_node/DTLS-sessions.html') diff --git a/manual/html_node/DTLS-sessions.html b/manual/html_node/DTLS-sessions.html index bf2e3cd453..9f2b1800b8 100644 --- a/manual/html_node/DTLS-sessions.html +++ b/manual/html_node/DTLS-sessions.html @@ -1,7 +1,7 @@ - -GnuTLS 3.3.6: DTLS sessions +GnuTLS 3.3.7: DTLS sessions - - + + @@ -167,7 +167,7 @@ Previous: Because datagram TLS can operate over connections where the client cannot be reliably verified, functionality in the form of cookies, is available to prevent denial of service attacks to servers. GnuTLS requires a server -to generate a secret key that is used to sign a cookie11. +to generate a secret key that is used to sign a cookie12. That cookie is sent to the client using gnutls_dtls_cookie_send, and the client must reply using the correct cookie. The server side should verify the initial message sent by client using gnutls_dtls_cookie_verify. @@ -204,7 +204,7 @@ a path MTU discovery mechanism [RFC4821].

Footnotes

-

(11)

+

(12)

A key of 128 bits or 16 bytes should be sufficient for this purpose.

-- cgit v1.2.1