puts( headers);
-printf("\\begin{supertabular}{|l|p{1cm}|p{3.5cm}|}\n\\label{tab:alerts}\n");
+printf("\\begin{supertabular}{|p{.50\\linewidth}|p{.07\\linewidth}|p{.34\\linewidth}|}\n\\label{tab:alerts}\n");
{
size_t i;
These signals are mostly used to inform the peer about the cause of a
protocol failure. Some of these signals are used internally by the
protocol and the application protocol does not have to cope with them
-(e.g. @code{GNUTLS_A_CLOSE_NOTIFY}), and others refer to the
-application protocol solely (e.g. @code{GNUTLS_A_USER_CANCELLED}). An
+(e.g. @code{GNUTLS_\-A_\-CLOSE_\-NOTIFY}), and others refer to the
+application protocol solely (e.g. @code{GNUTLS_\-A_\-USER_\-CANCELLED}). An
alert signal includes a level indication which may be either fatal or
warning. Fatal alerts always terminate the current connection, and
prevent future re-negotiations using the current session ID. All alert
@include alerts.texi
-
@node The TLS Handshake Protocol
@section The TLS handshake protocol
@anchor{The Handshake Protocol}
@acronym{GnuTLS} consists of three independent parts, namely the ``TLS
protocol part'', the ``Certificate part'', and the ``Cryptographic
-back-end'' part. The `TLS protocol part' is the actual protocol
+back-end'' part. The ``TLS protocol part'' is the actual protocol
implementation, and is entirely implemented within the
-@acronym{GnuTLS} library. The `Certificate part' consists of the
+@acronym{GnuTLS} library. The ``Certificate part'' consists of the
certificate parsing, and verification functions which is partially
implemented in the @acronym{GnuTLS} library. The
libtasn1@footnote{@url{http://www.gnu.org/software/libtasn1/}},
Fatal errors terminate the connection immediately and further sends
and receives will be disallowed. Such an example is
-@code{GNUTLS_E_DECRYPTION_FAILED}. Non-fatal errors may warn about
+@code{GNUTLS_\-E_\-DECRYPTION_\-FAILED}. Non-fatal errors may warn about
something, i.e., a warning alert was received, or indicate the some
action has to be taken. This is the case with the error code
-@code{GNUTLS_E_REHANDSHAKE} returned by @funcref{gnutls_record_recv}.
+@code{GNUTLS_\-E_\-REHANDSHAKE} returned by @funcref{gnutls_record_recv}.
This error code indicates that the server requests a re-handshake. The
client may ignore this request, or may reply with an alert. You can
test if an error code is a fatal one by using the
@cindex srptool
The @file{srptool} is a very simple program that emulates the programs
-in the @emph{Stanford SRP libraries}, see
-@url{http://srp.stanford.edu/}. It is intended for use in places
+in the @emph{Stanford SRP libraries}@footnote{See
+@url{http://srp.stanford.edu/}.}. It is intended for use in places
where you don't expect @acronym{SRP} authentication to be the used for
system users.
puts( headers);
-printf("\\begin{supertabular}{|l|p{6.3cm}|}\n");
+printf("\\begin{supertabular}{|p{.52\\linewidth}|p{.40\\linewidth}|}\n");
memset( names_to_sort, 0, sizeof(names_to_sort));
j=0;
desc = gnutls_strerror( names_to_sort[i].error_index);
if (desc == NULL || _name == NULL) continue;
- printf( "{\\tiny{%s}} & %s", escape_string(_name, buffer1, sizeof(buffer1)), escape_string(desc, buffer2, sizeof(buffer2)));
+ printf( "{\\scriptsize{%s}} & %s", escape_string(_name, buffer1, sizeof(buffer1)), escape_string(desc, buffer2, sizeof(buffer2)));
printf( "\\\\\n");
}
puts( headers);
-printf("\\begin{supertabular}{|l|p{1.8cm}|p{1.6cm}|}\n");
+printf("\\begin{supertabular}{|p{.60\\linewidth}|p{.15\\linewidth}|p{.10\\linewidth}|}\n");
{
size_t i;