MSCHAP failing on new 2.1.10 install

[Gary Gatten]

I ended up doing something similar, so yeah that will work.  Lots of ways to do it I guess.  At minimum perhaps a BIG WARNING in the README's telling you to not make file backups in the "live" directories.  Or, maybe do something like the sites directory for modules and others: modules-available and modules-enabled?  That would work for me too.

G




-----Original Message-----
From: freeradius-users-bounces+ggatten=waddell.com at lists.freeradius.org [mailto:freeradius-users-bounces+ggatten=waddell.com at lists.freeradius.org] On Behalf Of Alan Buxey
Sent: Wednesday, May 11, 2011 4:46 PM
To: FreeRadius users mailing list
Subject: Re: MSCHAP failing on new 2.1.10 install

Hi,
> Quick test shows this is working now.  Not tested enough yet to claim victory, but I'm not scratching my head going WTF....  I VAGUELY recall burning myself several years ago when I started playing with FR, hence why I remembered it - finally!
> 
> If I feel froggy I MAY tweak the source and submit a "patch" to ignore files with any extension.  Of course some people may not like that...  Perhaps a seting in radiusd.conf with file extensions to ignore; such as .bak, .org, etc.  Anything in that list would be ignored...  I like that one, but since I can't code worth a $hit it would take me a LONG time for this one.  Maybe I can/will submit a feature request for such a thing...

there was similar discussion end of last year or so.....my view is that you
just make a new directory eg sites-old and dump the old configs or backups into
there...they wont get read then  :-)

alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html





<font size="1">
<div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'>
</div>
"This email is intended to be reviewed by only the intended recipient
 and may contain information that is privileged and/or confidential.
 If you are not the intended recipient, you are hereby notified that
 any review, use, dissemination, disclosure or copying of this email
 and its attachments, if any, is strictly prohibited.  If you have
 received this email in error, please immediately notify the sender by
 return email and delete this email from your system."
</font>