gsasl-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CVS gsasl/doc


From: gsasl-commit
Subject: CVS gsasl/doc
Date: Thu, 30 Sep 2004 17:06:34 +0200

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

Modified Files:
        gsasl.texi 
Log Message:
Fix.


--- /home/cvs/gsasl/doc/gsasl.texi      2004/09/30 13:56:00     1.73
+++ /home/cvs/gsasl/doc/gsasl.texi      2004/09/30 15:06:34     1.74
@@ -104,7 +104,7 @@
 The library is easily ported because it does not do network
 communication by itself, but rather leaves it up to the calling
 application.  The library is flexible with regards to the
-authorization infrastructure used, as it utilizes callbacks into the
+authorization infrastructure used, as it utilize a callback into the
 application to decide whether a user is authorized or not.
 
 GNU SASL is developed for the GNU/Linux system, but runs on over 20
@@ -118,8 +118,8 @@
 fits in under 60kb on an Intel x86 platform, without any modifications
 to the code.  (This figure was accurate as of version 0.0.13.)
 
-Most of the library is licensed under the GNU Lesser General Public
-License, but the command-line interface and self-tests are licensed
+The library is licensed under the GNU Lesser General Public License,
+and the command-line interface, self-tests and examples are licensed
 under the GNU General Public License.
 
 @menu
@@ -165,7 +165,7 @@
 
 @item It's thread-safe
 No global variables are used and multiple library handles and session
-handles may be used in parallell.
+handles may be used in parallel.
 
 @item It's internationalized
 It handles non-ASCII username and passwords and user visible strings
@@ -181,7 +181,7 @@
 
 Note that the library do not implement any policy to decide whether a
 certain user is ``authenticated'' or ``authorized'' or not.  Rather,
-it uses callbacks back into the application to answer these questions.
+it uses a callback into the application to answer these questions.
 
 @node SASL Overview
 @section SASL Overview
@@ -419,8 +419,8 @@
 @url{http://josefsson.org/gsasl/releases/}
 
 The latest version is stored in a file, e.g.,
address@hidden where the @samp{0.0.42} indicate the
-highest version number.
address@hidden@value{VERSION}.tar.gz} where the @address@hidden
+value is the highest version number in the directory.
 
 The package is then extracted, configured and built like many other
 packages that use Autoconf.  For detailed information on configuring
@@ -624,11 +624,48 @@
 initialized by calling @code{gsasl_init} (@pxref{Global Functions}).
 The resources allocated by the initialization process can be released
 if the application no longer has a need to call `Libgsasl' functions,
-this is done by calling @code{gsasl_done}.
+this is done by calling @code{gsasl_done}.  For example:
 
-In order to take advantage of the internationalisation features in the
-library, such as translated error messages, the application must set
-the current locale using @code{setlocale} before initialization.
address@hidden
+int
+main (int argc, char *argv[])
address@hidden
+  Gsasl_ctx *ctx = NULL;
+  int rc;
+...
+  rc = gsasl_init (&ctx);
+  if (rc != GSASL_OK)
+    @{
+      printf ("SASL initialization failure (%d): %s\n",
+              rc, gsasl_strerror (rc));
+      return 1;
+    @}
+...
address@hidden example
+
+In order to make error messages from @code{gsasl_strerror} be
+translated (@pxref{Top,,,gettext,GNU Gettext}) the application must
+set the current locale using @code{setlocale} before calling
address@hidden  For example:
+
address@hidden
+int
+main (int argc, char *argv[])
address@hidden
+  Gsasl_ctx *ctx = NULL;
+  int rc;
+...
+  setlocale (LC_ALL, "");
+...
+  rc = gsasl_init (&ctx);
+  if (rc != GSASL_OK)
+    @{
+      printf (gettext ("SASL initialization failure (%d): %s\n"),
+              rc, gsasl_strerror (rc));
+      return 1;
+    @}
+...
address@hidden example
 
 In order to take advantage of the secure memory features in
 address@hidden that GNU SASL can also use Nettle for the
@@ -641,12 +678,12 @@
 @example
 #include <gcrypt.h>
 ...
-
 int
 main (int argc, char *argv[])
 @{
+  Gsasl_ctx *ctx = NULL;
+  int rc;
 ...
-
   /* Check version of libgcrypt. */
   if (!gcry_check_version (GCRYPT_VERSION))
     die ("version mismatch\n");
@@ -657,7 +694,15 @@
 
   /* Tell Libgcrypt that initialization has completed. */
   gcry_control (GCRYCTL_INITIALIZATION_FINISHED, 0);
-  ...
+...
+  rc = gsasl_init (&ctx);
+  if (rc != GSASL_OK)
+    @{
+      printf ("SASL initialization failure (%d): %s\n",
+              rc, gsasl_strerror (rc));
+      return 1;
+    @}
+...
 @end example
 
 If you do not do this, keying material will not be allocated in secure





reply via email to

[Prev in Thread] Current Thread [Next in Thread]