On 13/04/11 16:22, Alan DeKok wrote:
Phil Mayers wrote:
Actually, I was just testing this and proxying the inner EAP-MSCHAPv2 as plain MS-CHAPv2 seems to be broken, at least in my testing. It doesn't crash the server, but equally it doesn't pass the S=XXX success back correctly either, so the client does a PEAP reject.
Hmm... OK.
It seems as if the rlm_eap_mshcapv2 post_proxy function isn't working somehow; I am trying to perform a "git bisect" to find when it stopped working, but am running into problems with the commits which don't build :o(
Sorry... we really need a test infrastructure.
No worries; it seems to be broken for 2.1.7 and 2.1.8, but worked in 2.1.1 - still trying to track it down more tightly than that. (We don't actually use this feature so I'm not that fussed, but I'm determine to wrestle "git bisect" into submission ;o)