Explorar el Código

AUTH minor documentation updates

Olle E. Johansson hace 13 años
padre
commit
15fdde4fa1
Se han modificado 2 ficheros con 12 adiciones y 11 borrados
  1. 6 5
      modules/auth/README
  2. 6 6
      modules/auth/doc/params.xml

+ 6 - 5
modules/auth/README

@@ -443,15 +443,16 @@ modparam("auth", "otn_in_flight_order", 23)   # 8 Mb (1Mb memory)
 
 1.3.10. secret (string)
 
-   Secret phrase used to calculate the nonce value. The default is to use
-   a random value generated from the random source in the core.
+   Secret phrase used to calculate the nonce value used to challenge the
+   client for authentication.
 
    If you use multiple servers in your installation, and would like to
    authenticate on the second server against the nonce generated at the
    first one its necessary to explicitly set the secret to the same value
-   on all servers. However, the use of a shared (and fixed) secret as
-   nonce is insecure, much better is to stay with the default. Any clients
-   should send the reply to the server that issued the request.
+   on all servers. However, as the use of a shared (and fixed) secret as
+   nonce is insecure, it is much better is to stay with the default. Any
+   clients should send the authenticated request to the server that issued
+   the challenge.
 
    Default value is randomly generated string.
 

+ 6 - 6
modules/auth/doc/params.xml

@@ -548,15 +548,15 @@ modparam("auth", "otn_in_flight_order", 23)   # 8 Mb (1Mb memory)
 
     <section id="auth.secret">
 	<title><varname>secret</varname> (string)</title>
-	<para>Secret phrase used to calculate the nonce value.
-	The default is to use a random value generated from the random source
-	in the core.</para>
+	<para>Secret phrase used to calculate the nonce value used to challenge
+	the client for authentication.</para>
 	<para>If you use multiple servers in your installation, and would like to
 	authenticate on the second server against the nonce generated at the
 	first one its necessary to explicitly set the secret to the same value
-	on all servers. However, the use of a shared (and fixed) secret as
-	nonce is insecure, much better is to stay with the default. Any
-	clients should send the reply to the server that issued the request.
+	on all servers. However, as the use of a shared (and fixed) secret as
+	nonce is insecure, it is much better is to stay with the default. Any
+	clients should send the authenticated request to the server that 
+	issued the challenge.
 	</para>
 	<para>
 	    Default value is randomly generated string.