[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS gsasl/doc
From: |
gsasl-commit |
Subject: |
CVS gsasl/doc |
Date: |
Sun, 07 Nov 2004 17:35:46 +0100 |
Update of /home/cvs/gsasl/doc
In directory dopio:/tmp/cvs-serv9187
Modified Files:
gsasl.texi
Log Message:
Fix.
--- /home/cvs/gsasl/doc/gsasl.texi 2004/11/07 16:26:50 1.93
+++ /home/cvs/gsasl/doc/gsasl.texi 2004/11/07 16:35:46 1.94
@@ -1312,10 +1312,9 @@
application using it. To handle these differences the library can use
a callback function into your application in several different ways.
Some mechanisms, such as @samp{PLAIN}, are simple to explain and use.
-The client callback for these mechanisms should query the user for a
-username and password. The server callback hand the username and
-password into any local policy deciding authentication system (such as
address@hidden/etc/passwd} via PAM).
+The client callback query the user for a username and password. The
+server callback hand the username and password into any local policy
+deciding authentication system (such as @file{/etc/passwd} via PAM).
Mechanism such as @samp{CRAM-MD5} and @samp{DIGEST-MD5} uses hashed
passwords. The client callback are the same as for PLAIN. However,
- CVS gsasl/doc, gsasl-commit, 2004/11/05
- CVS gsasl/doc, gsasl-commit, 2004/11/05
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc,
gsasl-commit <=
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/07
- CVS gsasl/doc, gsasl-commit, 2004/11/13
- CVS gsasl/doc, gsasl-commit, 2004/11/18
- CVS gsasl/doc, gsasl-commit, 2004/11/18
- CVS gsasl/doc, gsasl-commit, 2004/11/18
- CVS gsasl/doc, gsasl-commit, 2004/11/23
- CVS gsasl/doc, gsasl-commit, 2004/11/23