added gtc{} to eap{}

diff --git a/raddb/radiusd.conf.in b/raddb/radiusd.conf.in
index 9030c10..1b5a338 100644 (file)
--- a/raddb/radiusd.conf.in
+++ b/raddb/radiusd.conf.in
@@ -672,6 +672,37 @@ modules {
                leap {
                }
 
+               #  Generic Token Card.
+               #  
+               #  Currently, this is only permitted inside of EAP-TTLS,
+               #  or EAP-PEAP.  The module "challenges" the user with
+               #  text, and the response from the user is taken to be
+               #  the User-Password.
+               #
+               #  Proxying the tunneled EAP-GTC session is a bad idea,
+               #  the users password will go over the wire in plain-text,
+               #  for anyone to see.
+               #
+               gtc {
+                       #  The default challenge, which many clients
+                       #  ignore..
+                       #challenge = "Password: "
+
+                       #  The plain-text response which comes back
+                       #  is put into a User-Password attribute,
+                       #  and passed to another module for
+                       #  authentication.  This allows the EAP-GTC
+                       #  response to be checked against plain-text,
+                       #  or crypt'd passwords.
+                       #
+                       #  If you say "Local" instead of "PAP", then
+                       #  the module will look for a User-Password
+                       #  configured for the request, and do the
+                       #  authentication itself.
+                       #
+                       auth_type = PAP
+               }
+
                ## EAP-TLS
                #
                #  To generate ctest certificates, run the script