On Thu, 2004-01-08 at 16:19, Alan DeKok wrote:
John Horne [EMAIL PROTECTED] wrote:
This seemed to make no difference. However I did notice, before and
after the change, that if the user file entry has something like:
User-Password != something
Then if the user enters the
John Horne [EMAIL PROTECTED] wrote:
Given that, I assume then that it is then not possible to create a
default 'users' file entry which will allow *any* user through if we
insist on using MS-CHAPv2?
Auth-Type := Accept
Will allow the user through, without password checking.
Alan
On Thu, 2004-01-08 at 16:48, Alan DeKok wrote:
John Horne [EMAIL PROTECTED] wrote:
Given that, I assume then that it is then not possible to create a
default 'users' file entry which will allow *any* user through if we
insist on using MS-CHAPv2?
Auth-Type := Accept
Will allow the
John Horne [EMAIL PROTECTED] wrote:
Will allow the user through, without password checking.
No it doesn't - I tried that after reading the FAQ. If I use just:
jhornexAuth-Type := Accept
then radiusd complains that no MSCHAP password has been supplied:
Which is why I
John Horne [EMAIL PROTECTED] wrote:
As can be seen it says 'Login OK' but seems to be missing the:
Sending Access-Accept of id 209 to 127.0.0.1:40603
MS-CHAP2-Success =
0x01533d36364635423233344331414344363438463746353946443832353834324437424131433645464332
Ah, yes. For that,
John Horne [EMAIL PROTECTED] wrote:
...
This all works fine; the user is authenticated and radiusd sees that
MS-CHAPv2 is being used (and is to be used).
Hmm... so MS-CHAPv2 works, as I suspected. Recent discussion on the
list says it's broken on some systems, but I don't know why.
Hello,
I have been asked to run through some disaster recovery checks for our
servers, and one (pair) of these servers runs RADIUS but does so in
order to talk to a Microsoft IAS server (for the actual authentication).
In the event of a disaster the IAS server may be lost, and as such I
would
7 matches
Mail list logo
