To initiate the handshake.
@end table
+@menu
+* TLS Cipher Suites:: TLS session parameters.
+* Priority Strings:: Defining how parameters are negotiated.
+* Client Authentication:: Requesting a certificate from the client.
+* Resuming Sessions:: Reusing previously established keys.
+@end menu
+
+@node TLS Cipher Suites
@subsection TLS Cipher Suites
The Handshake Protocol of @acronym{TLS} negotiates cipher suites of
All the supported ciphersuites are shown in @ref{ciphersuites}.
-@subsection Priority strings
+@node Priority Strings
+@subsection Priority Strings
In order to specify cipher suite preferences, the
previously shown priority functions accept a string
that specifies the algorithms to be enabled in a TLS handshake.
@end table
+@node Client Authentication
@subsection Client Authentication
@cindex Client Certificate authentication
@ref{gnutls_certificate_send_x509_rdn_sequence}. The client, then, may
send a certificate, signed by one of the server's acceptable signers.
+@node Resuming Sessions
@subsection Resuming Sessions
@anchor{resume}
@cindex Resuming sessions
(SCM session, SCM priorities),
"Have @var{session} use the given @var{priorities} for "
"the ciphers, key exchange methods, MACs and compression "
- "methods. @var{priorities} must be a string; see the "
- "manual for the syntax. When @var{priorities} cannot be "
+ "methods. @var{priorities} must be a string (@pxref{"
+ "Priority Strings}). When @var{priorities} cannot be "
"parsed, an @code{error/invalid-request} error is raised, "
"with an extra argument indication the position of the "
"error.\n")