Re: NT hashed password in userPassword attribute.

Jason Howk Mon, 14 Feb 2005 12:38:27 -0800

No go. I put in some additional debug statements and recompiled eap_leap and I'm seeing some interesting results. If I follow what is described below, the output from the call to eapleap_ntpwdhash()(eap_leap.c:198) is totally different if I revert back to using the LDAP ntPassword attribute with a valid octet string that starts with '0x'. The passwords used in each test are exactly the same so I would expect that the password to be hashed should be equivalent regardless of method. This isn't happening...

--Jason.

On Feb 14, 2005, at 10:40 AM, Alan DeKok wrote:

Jason Howk <[EMAIL PROTECTED]> wrote:

rlm_attr_rewrite: Changed value for attribute NT-Password from
'{NT}8846F7EAEE8FB117AD06BDD830B7586C' to
'0x8846F7EAEE8FB117AD06BDD830B7586C'


  You should remove the {NT} header, and nothing more All of the code
in the server which uses NT-Password will accept the hex format.

  Alan DeKok.

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: NT hashed password in userPassword attribute.

Reply via email to