Dear Michael Lecuyer, There is a _lot_ of bugs in RFC2759. But name is clearly defined as ASCII for response packet:
The Name field is a string of 0 to (theoretically) 256 case-sensitive ASCII characters which identifies the peer's user account name. The Windows NT domain name may prefix the user's account name (e.g. "BIGCO\johndoe" where "BIGCO" is a Windows NT domain containing the user account "johndoe"). If a domain is not provided, the backslash should also be omitted, (e.g. "johndoe"). --Thursday, June 20, 2002, 8:55:31 PM, you wrote to [EMAIL PROTECTED]: ML> In the MS-CHAP 2 RFC it's claimed that the user name should be in Unicode ML> like the password. ML> Examining the code in rlm_mschap.c the user name is not converted to ML> unicode before the hashing in challenge_hash(). Examining just what was in ML> the user_name before the showed it was just regular ASCII (unlike the ML> unicode version of the password elsewhere). ML> Is this what actually happens in practice? ML> - ML> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- ~/ZARAZA ������ �������� ���������� ����������. (���) - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
