[SCM] GNU gsasl branch, master, updated. gsasl-1-2-105-g577799d

[Simon Josefsson]

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 gsasl".

http://git.savannah.gnu.org/cgit/gsasl.git/commit/?id=577799d4584b5e9469d88eadbd69ecef9ee9cb6b

The branch, master has been updated
       via  577799d4584b5e9469d88eadbd69ecef9ee9cb6b (commit)
      from  f411ee0005a6076c416a9210edbbaca210101c4b (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 577799d4584b5e9469d88eadbd69ecef9ee9cb6b
Author: Simon Josefsson <address@hidden>
Date:   Thu Oct 8 16:21:28 2009 +0200

    Fix.

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

Summary of changes:
 doc/gsasl.texi |    9 ++++-----
 1 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/gsasl.texi b/doc/gsasl.texi
index 020c598..608c96f 100644
--- a/doc/gsasl.texi
+++ b/doc/gsasl.texi
@@ -1704,13 +1704,12 @@ values offered by the server (which may be inspected 
through the
 @section The SCRAM-SHA-1 mechanism
 @cindex SCRAM
 
-The SCRAM-SHA-1 mechanism is designed to provide most of the same
-features as CRAM-MD5 and DIGEST-MD5 but use modern cryptographic
-algorithms such as HMAC-SHA-1 and PKCS#5 PBKDF2.  It supports
+The SCRAM-SHA-1 mechanism is designed to provide (almost) the same
+capabilities as CRAM-MD5 and DIGEST-MD5 but use modern cryptographic
+techniques such as HMAC-SHA-1 and PKCS#5 PBKDF2.  SCRAM-SHA-1 supports
 authorization identities.  Like CRAM-MD5 and DIGEST-MD5, only a hashed
 password is transferred.  Consequently, SCRAM-SHA-1 needs access to
-the correct password (although it may be hashed) to verify the client
-response.
+the correct password to verify the client response.
 
 In the client, this mechanism is always enabled, and it requires the
 @code{GSASL_AUTHID} property, and either @code{GSASL_PASSWORD} or


hooks/post-receive
-- 
GNU gsasl