1 diff -ruN freeradius-1.0.2-orig/raddb/eap.conf freeradius-1.0.2-2/raddb/eap.conf
2 --- freeradius-1.0.2-orig/raddb/eap.conf 2004-04-15 20:34:41.000000000 +0200
3 +++ freeradius-1.0.2-2/raddb/eap.conf 2005-03-13 23:05:13.000000000 +0100
5 # User-Password, or the NT-Password attributes.
6 # 'System' authentication is impossible with LEAP.
16 # the users password will go over the wire in plain-text,
21 # The default challenge, which many clients
23 #challenge = "Password: "
25 # configured for the request, and do the
26 # authentication itself.
36 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not
45 diff -ruN freeradius-1.0.2-orig/raddb/radiusd.conf.in freeradius-1.0.2-2/raddb/radiusd.conf.in
46 --- freeradius-1.0.2-orig/raddb/radiusd.conf.in 2005-02-07 20:52:05.000000000 +0100
47 +++ freeradius-1.0.2-2/raddb/radiusd.conf.in 2005-03-13 23:05:13.000000000 +0100
50 # Location of config and logfiles.
52 -run_dir = ${localstatedir}/run/radiusd
53 +run_dir = ${localstatedir}/run
56 # The logging messages for the server are appended to the
59 -log_file = ${logdir}/radius.log
60 +log_file = ${localstatedir}/log/radiusd.log
63 # libdir: Where to find the rlm_* modules.
67 # The program to execute to do concurrency checks.
68 -checkrad = ${sbindir}/checkrad
69 +#checkrad = ${sbindir}/checkrad
71 # SECURITY CONFIGURATION
75 # allowed values: {no, yes}
78 -$INCLUDE ${confdir}/proxy.conf
80 +#$INCLUDE ${confdir}/proxy.conf
83 # CLIENTS CONFIGURATION
85 # 'snmp' attribute to 'yes'
88 -$INCLUDE ${confdir}/snmp.conf
89 +#$INCLUDE ${confdir}/snmp.conf
92 # THREAD POOL CONFIGURATION
94 # For all EAP related authentications.
95 # Now in another file, because it is very large.
97 -$INCLUDE ${confdir}/eap.conf
98 +# $INCLUDE ${confdir}/eap.conf
100 # Microsoft CHAP authentication
102 @@ -1034,7 +1034,7 @@
105 usersfile = ${confdir}/users
106 - acctusersfile = ${confdir}/acct_users
107 +# acctusersfile = ${confdir}/acct_users
109 # If you want to use the old Cistron 'users' file
110 # with FreeRADIUS, you should change the next line
111 @@ -1167,7 +1167,7 @@
112 # For MS-SQL, use: ${confdir}/mssql.conf
113 # For Oracle, use: ${confdir}/oraclesql.conf
115 - $INCLUDE ${confdir}/sql.conf
116 +# $INCLUDE ${confdir}/sql.conf
119 # For Cisco VoIP specific accounting with Postgresql,
120 @@ -1535,7 +1535,7 @@
121 # The entire command line (and output) must fit into 253 bytes.
123 # e.g. Framed-Pool = `%{exec:/bin/echo foo}`
128 # The expression module doesn't do authorization,
129 @@ -1548,7 +1548,7 @@
130 # listed in any other section. See 'doc/rlm_expr' for
137 # We add the counter module here so that it registers
138 @@ -1575,7 +1575,7 @@
139 # 'raddb/huntgroups' files.
141 # It also adds the %{Client-IP-Address} attribute to the request.
146 # If you want to have a log of authentication requests,
147 @@ -1588,7 +1588,7 @@
149 # The chap module will set 'Auth-Type := CHAP' if we are
150 # handling a CHAP request and Auth-Type has not already been set
155 # If the users are logging in with an MS-CHAP-Challenge
156 @@ -1596,7 +1596,7 @@
157 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
158 # to the request, which will cause the server to then use
159 # the mschap module for authentication.
164 # If you have a Cisco SIP server authenticating against
165 @@ -1616,7 +1616,7 @@
166 # Otherwise, when the first style of realm doesn't match,
167 # the other styles won't be checked.
174 @@ -1625,11 +1625,11 @@
176 # It also sets the EAP-Type attribute in the request
177 # attribute list to the EAP type from the packet.
182 # Read the 'users' file
187 # Look in an SQL database. The schema of the database
188 @@ -1683,24 +1683,24 @@
189 # PAP authentication, when a back-end database listed
190 # in the 'authorize' section supplies a password. The
191 # password can be clear-text, or encrypted.
200 # Most people want CHAP authentication
201 # A back-end database listed in the 'authorize' section
202 # MUST supply a CLEAR TEXT password. Encrypted passwords
212 # MSCHAP authentication.
213 - Auth-Type MS-CHAP {
216 +# Auth-Type MS-CHAP {
221 # If you have a Cisco SIP server authenticating against
222 @@ -1718,7 +1718,7 @@
223 # containing CHAP-Password attributes CANNOT be authenticated
224 # against /etc/passwd! See the FAQ for details.
229 # Uncomment it if you want to use ldap for authentication
231 @@ -1731,7 +1731,7 @@
234 # Allow EAP authentication.
240 @@ -1739,12 +1739,12 @@
241 # Pre-accounting. Decide which accounting type to use.
248 # Ensure that we have a semi-unique identifier for every
249 # request, and many NAS boxes are broken.
254 # Look for IPASS-style 'realm/', and if not found, look for
255 @@ -1754,12 +1754,12 @@
256 # Accounting requests are generally proxied to the same
257 # home server as authentication requests.
264 # Read the 'acct_users' file
270 @@ -1770,20 +1770,20 @@
271 # Create a 'detail'ed log of the packets.
272 # Note that accounting requests which are proxied
273 # are also logged in the detail file.
278 # Update the wtmp file
280 # If you don't use "radlast", you can delete this line.
285 # For Simultaneous-Use tracking.
287 # Due to packet losses in the network, the data here
288 # may be incorrect. There is little we can do about it.
293 # Return an address to the IP Pool when we see a stop record.
294 @@ -1806,7 +1806,7 @@
295 # or rlm_sql module can handle this.
296 # The rlm_sql module is *much* faster
302 # See "Simultaneous Use Checking Querie" in sql.conf
303 @@ -1900,5 +1900,5 @@
304 # hidden inside of the EAP packet, and the end server will
305 # reject the EAP request.