CVS gsasl/doc

[gsasl-commit]

Update of /home/cvs/gsasl/doc
In directory dopio:/tmp/cvs-serv9466

Modified Files:
        gsasl.texi 
Log Message:
Fix.


--- /home/cvs/gsasl/doc/gsasl.texi      2005/08/27 12:12:56     1.115
+++ /home/cvs/gsasl/doc/gsasl.texi      2005/10/07 13:58:43     1.116
@@ -691,12 +691,13 @@
 @end example
 
 In order to take advantage of the secure memory features in
address@hidden that GNU SASL can also use Nettle for the
-Crypto backend.  Take care to verify that GNU SASL really use
-Libgcrypt, if this is what you want.}, you need to initialize secure
-memory in your application, and for some platforms even make your
-application setuid root.  See the Libgcrypt documentation for more
-information.  Example code to initialize secure memory in your code:
address@hidden that GNU SASL normally use its own internal
+implementation of the cryptographic functions.  Take care to verify
+that GNU SASL really use Libgcrypt, if this is what you want.}, you
+need to initialize secure memory in your application, and for some
+platforms even make your application setuid root.  See the Libgcrypt
+documentation for more information.  Example code to initialize secure
+memory in your code:
 
 @example
 #include <gcrypt.h>
@@ -1801,6 +1802,8 @@
 by Simon Josefsson.  The GSSAPI mechanism uses a GSS-API
 implementation, such as GSSLib by Simon Josefsson.
 
+Gnulib is used to simplify portability.
+
 This manual borrows text from the SASL specification.
 
 @c **********************************************************