MS-CHAP-V2 with no retry

[James J J Hooper]

On 08/04/2011 08:54, Alan DeKok wrote:
> Phil Mayers wrote:
>> +1 - In my experience it's necessary to cater for windows' weirdness
>> *first*. Most other clients have sane behaviours. I'm concerned about
>> the "we didn't do much windows testing" line...
>
>    Yup.
>
>    I've just pushed some changes to the git "v2.1.x" branch.  See:
>
> raddb/modules/mschap
> 	- allow_retry
> 	- retry_msg
>
> raddb/eap.socn
> 	- send_error
>
>    The default is no change.  See the documentation for how to test the
> new features.

Hi Alan,

I've may have mis-understood the code, but I think the EAP MS-CHAP-v2 
Failure packet, should be an EAP *request* (currently it's EAP failure)??

http://tools.ietf.org/html/draft-kamath-pppext-eap-mschapv2-01#page-12

...as per attached diff?

-James
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p3.txt.gz
Type: application/x-gzip
Size: 340 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110409/ec88bc7c/attachment.bin>