Re: MS-CHAPv2, allow_retry=yes, but no code to handle the retry?

2012-04-12 Thread Alan DeKok
James J J Hooper wrote: Ok - More delving into the code (rlm_eap_mschapv2.c) seems to indicate that the bits missing in 2.1.x are possibly there in FR3: It might be useful to get that into the 2.1.x stream... Alan DeKok. - List info/subscribe/unsubscribe? See

MS-CHAPv2, allow_retry=yes, but no code to handle the retry?

2012-04-11 Thread James J J Hooper
Hi All, FR 2.1.x Git, doing PEAP against AD via ntlm_auth. I thought that with: allow_retry = yes [in modules/mschap] and send_error = yes [in modules/eap] ...FR has the functionality to take the second password attempt, and re-try it against AD i.e. The scenario outlined in section 9.1.4 of

Re: MS-CHAPv2, allow_retry=yes, but no code to handle the retry?

2012-04-11 Thread James J J Hooper
On 11/04/2012 17:24, James J J Hooper wrote: Hi All, FR 2.1.x Git, doing PEAP against AD via ntlm_auth. I thought that with: allow_retry = yes [in modules/mschap] and send_error = yes [in modules/eap] ...FR has the functionality to take the second password attempt, and re-try it against AD