13 Apr
2011
13 Apr
'11
11:22 a.m.
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. Alan DeKok.