[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: |
Tue, 12 Oct 2004 22:32:30 +0200 |
Update of /home/cvs/gsasl/doc
In directory dopio:/tmp/cvs-serv2928
Modified Files:
gsasl.texi
Log Message:
Typo.
--- /home/cvs/gsasl/doc/gsasl.texi 2004/10/12 20:23:57 1.82
+++ /home/cvs/gsasl/doc/gsasl.texi 2004/10/12 20:32:29 1.83
@@ -1089,7 +1089,8 @@
an authorization identity, a special PIN or passcode, a realm, a
hostname, a service name, or an anonymous identifier. Querying the
user for all that information, without knowing exactly which of it is
-really needed is bad user design.
+really needed will result in a poor user interface. The user should
+not have to input private information, if it isn't required.
The approach is a bad idea for another reason. What if the server
abort the authentication process? Then your application have already
- CVS gsasl/doc, (continued)
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/03
- CVS gsasl/doc, gsasl-commit, 2004/10/04
- CVS gsasl/doc, gsasl-commit, 2004/10/04
- CVS gsasl/doc, gsasl-commit, 2004/10/04
- CVS gsasl/doc, gsasl-commit, 2004/10/12
- CVS gsasl/doc,
gsasl-commit <=
- CVS gsasl/doc, gsasl-commit, 2004/10/15
- CVS gsasl/doc, gsasl-commit, 2004/10/28
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31
- CVS gsasl/doc, gsasl-commit, 2004/10/31