[SCM] GNU gnutls branch, master, updated. gnutls_3_0_0-96-g0fc63a0

[Nikos Mavrogiannopoulos]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU gnutls".

http://git.savannah.gnu.org/cgit/gnutls.git/commit/?id=0fc63a0143381cfc54451f1c9501c447d84f8465

The branch, master has been updated
       via  0fc63a0143381cfc54451f1c9501c447d84f8465 (commit)
       via  d7c02407eb8eef708b1b298babf30b8bc58147f5 (commit)
      from  5b090f6e09444258cdebd1d0c179e40e9dceb749 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0fc63a0143381cfc54451f1c9501c447d84f8465
Author: Nikos Mavrogiannopoulos <address@hidden>
Date:   Sat Aug 20 23:57:41 2011 +0200

    Use texinfo's word break.

-----------------------------------------------------------------------

Summary of changes:
 NEWS                     |    8 ++++----
 doc/cha-cert-auth.texi   |   28 ++++++++++++++--------------
 doc/cha-internals.texi   |   32 +++++++++++++++++---------------
 doc/cha-intro-tls.texi   |    4 ++--
 doc/cha-library.texi     |    4 ++--
 doc/scripts/mytexi2latex |    1 +
 m4/hooks.m4              |    2 +-
 7 files changed, 41 insertions(+), 38 deletions(-)

diff --git a/NEWS b/NEWS
index 330f031..ac988de 100644
--- a/NEWS
+++ b/NEWS
@@ -2,7 +2,7 @@ GnuTLS NEWS -- History of user-visible changes.                
-*- outline -*-
 Copyright (C) 2000-2011 Free Software Foundation, Inc.
 See the end for copying conditions.
 
-* Version 3.0.1 (unreleased)
+* Version 3.0.1 (released 2011-08-20)
 
 ** libgnutls: gnutls_certificate_set_x509_key_file() and 
 friends support server name indication. If multiple 
@@ -24,9 +24,9 @@ modules.
 ** libgnutls: The config file at gnutls_pkcs11_init()
 is being read if provided.
 
-** libgnutls: Verify that a certificate list specified
-using gnutls_certificate_set_x509_key*(), is sorted
-according to TLS specification (from subject to issuer).
+** libgnutls: Ensure that a certificate list specified
+using gnutls_certificate_set_x509_key() and friends, is 
+sorted according to TLS specification (from subject to issuer).
 
 ** libgnutls: Added GNUTLS_X509_CRT_LIST_FAIL_IF_UNSORTED flag for
 gnutls_x509_crt_list_import. It checks whether the list to be 
diff --git a/doc/cha-cert-auth.texi b/doc/cha-cert-auth.texi
index cce8acc..c1c0ddf 100644
--- a/doc/cha-cert-auth.texi
+++ b/doc/cha-cert-auth.texi
@@ -156,7 +156,7 @@ provided.
 
 The verification function will verify a given certificate chain against a list 
of certificate
 authorities and certificate revocation lists, and output
-a bit-wise OR of elements of the @code{gnutls_\-certificate_\-status_t} 
+a bit-wise OR of elements of the @address@hidden@-status_t} 
 enumeration. 
 A detailed description of these elements can be found 
 in @ref{tab:cert-verify}. An example of certificate verification is shown in 
@ref{ex:verify2}.
@@ -218,42 +218,42 @@ flags are part of the enumeration
 @multitable @columnfractions .5 .5
 
 @headitem Flag @tab Description
address@hidden GNUTLS_VERIFY_\-DISABLE_CA_SIGN @tab
address@hidden address@hidden @tab
 If set a signer does not have to be a certificate authority. This
 flag should normally be disabled, unless you know what this means.
 
address@hidden GNUTLS_VERIFY_\-ALLOW_X509_V1_CA_CRT @tab
address@hidden address@hidden @tab
 Allow only trusted CA certificates that have version 1.  This is
-safer than GNUTLS_VERIFY_\-ALLOW_ANY_X509_V1_CA_CRT, and should be
+safer than address@hidden, and should be
 used instead. That way only signers in your trusted list will be
 allowed to have certificates of version 1. This is the default.
 
address@hidden GNUTLS_VERIFY_\-DO_NOT_ALLOW_X509_V1_CA_CRT @tab
address@hidden address@hidden @tab
 Do not allow trusted version 1 CA certificates.  This option is to be used
 in order consider all V1 certificates as deprecated.
 
address@hidden GNUTLS_VERIFY_\-ALLOW_ANY_X509_V1_CA_CRT @tab
address@hidden address@hidden @tab
 Allow CA certificates that have version 1 (both root and
 intermediate). This is dangerous since those haven't the
 basicConstraints extension. Must be used in combination with
-GNUTLS_VERIFY_\-ALLOW_X509_V1_CA_CRT.
address@hidden
 
address@hidden GNUTLS_VERIFY_\-DO_NOT_ALLOW_SAME @tab
address@hidden address@hidden @tab
 If a certificate is not signed by anyone trusted but exists in
 the trusted CA list do not treat it as trusted.
 
address@hidden GNUTLS_VERIFY_\-ALLOW_SIGN_RSA_MD2 @tab
address@hidden address@hidden @tab
 Allow certificates to be signed using the old MD2 algorithm.
 
address@hidden GNUTLS_VERIFY_\-ALLOW_SIGN_RSA_MD5 @tab
address@hidden address@hidden @tab
 Allow certificates to be signed using the broken MD5 algorithm.
 
address@hidden GNUTLS_VERIFY_\-DISABLE_TIME_CHECKS @tab
address@hidden address@hidden @tab
 Disable checking of activation
 and expiration validity periods of certificate chains. Don't set
 this unless you understand the security implications.
 
address@hidden GNUTLS_VERIFY_\-DISABLE_CRL_CHECKS @tab
address@hidden address@hidden @tab
 Disables checking for validity using certificate revocation lists.
 
 @end multitable
@@ -574,9 +574,9 @@ private key.
 
 With @acronym{GnuTLS} you can copy existing private keys and certificates
 to a token. Note that when copying private keys it is recommended to mark
-them as sensitive using the 
@code{GNUTLS_\-PKCS11_OBJ_\-FLAG_\-MARK_\-SENSITIVE}
+them as sensitive using the @address@hidden@address@hidden@-SENSITIVE}
 to prevent its extraction. An object can be marked as private using the flag 
address@hidden, to require PIN to be
address@hidden@address@hidden@address@hidden, to require PIN to be
 entered before accessing the object (for operations or otherwise).
 
 @showfuncdesc{gnutls_pkcs11_delete_url}
diff --git a/doc/cha-internals.texi b/doc/cha-internals.texi
index c0380fc..c442990 100644
--- a/doc/cha-internals.texi
+++ b/doc/cha-internals.texi
@@ -101,10 +101,10 @@ such as certificates, usernames etc. to 
@code{auth_info_t} structures.
 
 
 Simple examples of existing authentication methods can be seen in
address@hidden/\-psk.c} for PSK ciphersuites and @code{auth/\-srp.c} for SRP
address@hidden/@-psk.c} for PSK ciphersuites and @code{auth/@-srp.c} for SRP
 ciphersuites. After implementing these functions the structure holding
-its pointers has to be registered in @code{gnutls_\-algorithms.c} in the
address@hidden structure.
+its pointers has to be registered in @address@hidden in the
address@hidden@address@hidden structure.
 
 @node TLS Extension Handling
 @section TLS Extension Handling
@@ -123,7 +123,7 @@ and one for sending. These functions have to check 
internally whether
 they operate in client or server side. 
 
 A simple example of an extension handler can be seen in
address@hidden/\-srp.c} in GnuTLS' source code. After implementing these 
functions, 
address@hidden/@-srp.c} in GnuTLS' source code. After implementing these 
functions, 
 together with the extension number they handle, they have to be registered 
 using @funcintref{_gnutls_ext_register} in
 @code{gnutls_extensions.c} typically within @funcintref{_gnutls_ext_init}.
@@ -192,7 +192,7 @@ A typical entry would be:
 #endif
 @end example
 
-Most likely you'll need to add an @code{#include "ext/\-foobar.h"}, that
+Most likely you'll need to add an @code{#include "ext/@-foobar.h"}, that
 will contain something like
 like:
 @example
@@ -218,10 +218,12 @@ will be called to deinitialize the extension's private 
parameters, if any.
 Note that the conditional @code{ENABLE_FOOBAR} definition should only be 
 used if step 1 with the @code{configure} options has taken place.
 
address@hidden Add new files @code{ext/\-foobar.c} and @code{ext/\-foobar.h} 
that implement the extension.
address@hidden Add new files  that implement the extension.
 
 The functions you are responsible to add are those mentioned in the
-previous step.  As a starter, you could add this:
+previous step.  They should be added in a file such as @code{ext/@-foobar.c} 
+and headers should be placed in @code{ext/@-foobar.h}.
+As a starter, you could add this:
 
 @example
 int
@@ -259,15 +261,15 @@ The @funcintref{_foobar_send_params} function is 
responsible for
 sending extension data (both in the client and server).
 
 If you receive length fields that doesn't match, return
address@hidden  If you receive invalid
-data, return @code{GNUTLS_E_\-RECEIVED_\-ILLEGAL_\-PARAMETER}.  You can use
address@hidden@address@hidden@-LENGTH}.  If you receive invalid
+data, return @address@hidden@address@hidden  You can use
 other error codes from the list in @ref{Error codes}.  Return 0 on success.
 
 An extension typically stores private information in the @code{session}
 data for later usage. That can be done using the functions 
 @funcintref{_gnutls_ext_set_session_data} and
 @funcintref{_gnutls_ext_get_session_data}. You can check simple examples
-at @code{ext/\-max_\-record.c} and @code{ext/\-server_\-name.c} extensions.
+at @code{ext/@address@hidden and @code{ext/@address@hidden extensions.
 That private information can be saved and restored across session 
 resumption if the following functions are set:
 
@@ -308,7 +310,7 @@ _gnutls_foobar_send_params (gnutls_session_t session,
 
 The functions used would be declared as @code{static} functions, of
 the appropriate prototype, in the same file.
-When adding the files, you'll need to add them to @code{ext/\-Makefile.am}
+When adding the files, you'll need to add them to @code{ext/@-Makefile.am}
 as well, for example:
 
 @example
@@ -322,13 +324,13 @@ endif
 It might be desirable to allow users of the extension to
 request use of the extension, or set extension specific data.  
 This can be implemented by adding extension specific function calls
-that can be added to @code{includes/\-gnutls/\-gnutls.h},
+that can be added to @code{includes/@-gnutls/@-gnutls.h},
 as long as the LGPLv3+ applies.
-The implementation of the function should lie in the @code{ext/\-foobar.c} 
file.
+The implementation of the function should lie in the @code{ext/@-foobar.c} 
file.
 
 To make the API available in the shared library you need to add the
-symbol in @code{lib/\-libgnutls.map} or
address@hidden/\-libgnutls-\-extra.map} as appropriate, so that the symbol
+symbol in @code{lib/@-libgnutls.map} or
address@hidden/@address@hidden as appropriate, so that the symbol
 is exported properly.
 
 When writing GTK-DOC style documentation for your new APIs, don't
diff --git a/doc/cha-intro-tls.texi b/doc/cha-intro-tls.texi
index 3cc7941..623ba07 100644
--- a/doc/cha-intro-tls.texi
+++ b/doc/cha-intro-tls.texi
@@ -274,8 +274,8 @@ The alert protocol is there to allow signals to be sent 
between peers.
 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. @address@hidden@address@hidden), and others refer to the
+application protocol solely (e.g. @address@hidden@address@hidden).  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
diff --git a/doc/cha-library.texi b/doc/cha-library.texi
index c199439..2afaaa1 100644
--- a/doc/cha-library.texi
+++ b/doc/cha-library.texi
@@ -116,10 +116,10 @@ to be taken. Thus negative error codes may be fatal or 
not.
 
 Fatal errors terminate the connection immediately and further sends
 and receives will be disallowed.  Such an example is
address@hidden Non-fatal errors may warn about
address@hidden@address@hidden@-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
address@hidden returned by @funcref{gnutls_record_recv}.
address@hidden@address@hidden 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
diff --git a/doc/scripts/mytexi2latex b/doc/scripts/mytexi2latex
index 85ed327..53f88de 100755
--- a/doc/scripts/mytexi2latex
+++ b/doc/scripts/mytexi2latex
@@ -300,6 +300,7 @@ multitable:
                $line =~ s/\~/\\~/g;
                $line =~ s/\%(?!c)/\\%/g;
                $line =~ s/\#/\\\#/g;
+               $line =~ s/address@hidden/\\-/g;
                 $line =~ s/address@hidden (.*)/\\examplefile{\.\.\/$1}/g;
                $line =~ 
s/address@hidden($match+)\,($match+)\}/\\includegraphics\[width\=$2\]\{\.\.\/$1\.pdf\}/g;
                $line =~ s/address@hidden($spacematch+)\}/$1/g;
diff --git a/m4/hooks.m4 b/m4/hooks.m4
index dc052ff..6941e4f 100644
--- a/m4/hooks.m4
+++ b/m4/hooks.m4
@@ -41,7 +41,7 @@ AC_DEFUN([LIBGNUTLS_HOOKS],
   # Interfaces added:                             AGE++
   # Interfaces removed:                           AGE=0
   AC_SUBST(LT_CURRENT, 28)
-  AC_SUBST(LT_REVISION, 0)
+  AC_SUBST(LT_REVISION, 1)
   AC_SUBST(LT_AGE, 0)
 
   AC_SUBST(LT_SSL_CURRENT, 27)


hooks/post-receive
-- 
GNU gnutls