Problem with eap-peap

[Alan DeKok]

Trujillo Carmona, Antonio wrote:
...
> [mschapv2] +- entering group MS-CHAP {...} 
> [mschap] Told to do MS-CHAPv2 for gdxtrujo with NT-Password 
> [mschap] expand: --username=%{mschap:User-Name:-None} -> --username=gdxtrujo 
> [mschap] expand: --domain=%{mschap:NT-Domain:-HUVN} -> --domain=HUVN 
> [mschap] mschap2: 10 
> [mschap] expand: --challenge=%{mschap:Challenge:-00} -> --challenge=cacf5023c11e7ea7 
> [mschap] expand: --nt-response=%{mschap:NT-Response:-00} -> --nt-response=3e1277f2d4835fc8a8de7dfae71b2890c6ef6d3841140af2 
> Exec-Program output: NT_KEY: 2A28DA9AD2160A673F22F87D37D8E9BC 
> Exec-Program-Wait: plaintext: NT_KEY: 2A28DA9AD2160A673F22F87D37D8E9BC 
> Exec-Program: returned: 0 
...
> Sending Access-Challenge of id 50 to 10.104.16.128 port 45236
>  EAP-Message = 0x0109004a1900170301003f27dd660624182f35234bd9f80b3c7ad5c4ca8c538fc86c6bae1ba3991e4d3fd17f1a934ac2f7453801032ca9894b0d4a8687ceccbb61bb439c4c9fc642d244
>  Message-Authenticator = 0x00000000000000000000000000000000
>  State = 0x3cd4450c3bdd5c57a4c67a935e13b1f8
> Finished request 7.
> Going to the next request
> Waking up in 4.8 seconds.
> Cleaning up request 0 ID 43 with timestamp +35

  It's a bug in Samba.

  Downgrade Samba versions until it works.

  Alan DeKok.