Hello, Apparently the smbpasswd file doesn't care about mixed-case passwords. I've entered smbpasswd and changed my password to: MaEs. Then I did: smbclient //server/share -U werner and provided the wright password: MaEs. I managed to get access. BUT when I entered "maes" as password, it also worked. Same story with MAEs. Same story in Windows. Can anyone confirm this issue? Thanks alot, Werner Maes LUDIT-KULeuven
Hi Werner,
this behaviour is normal because the smbpasswd file contains passwords
that are encrypted in the Windows style. And Windows doesn't differ between
upper and lower case (passwords and usernames).
MfG PMD
----- Original Message -----
From: "werner maes" <werner.maes@cc.kuleuven.ac.be>
Newsgroups: comp.protocols.smb,linux.samba
To: <samba@samba.org>
Sent: Wednesday, January 31, 2001 5:59 PM
Subject: Smbpasswd and Mixed-case passwords
> Hello,
>
> Apparently the smbpasswd file doesn't care about mixed-case passwords.
> I've entered smbpasswd and changed my password to: MaEs.
> Then I did: smbclient //server/share -U werner and provided the wright
> password: MaEs. I managed to get access.
> BUT when I entered "maes" as password, it also worked. Same story
with
> MAEs.
>
> Same story in Windows.
> Can anyone confirm this issue?
>
> Thanks alot,
>
> Werner Maes
> LUDIT-KULeuven
>
>
Not entirely wrong... NT and 2K are particular about case, but win9x isn't. -----Original Message----- From: Pascal Deliot [mailto:pdeliot@ocare.com] Sent: Thursday, February 01, 2001 5:19 AM To: samba@us5.samba.org Subject: Re: Smbpasswd and Mixed-case passwords Wrong... Windows doesn't make the difference for username, but it does for password. Peter Michael D?ppenbecker wrote: > Hi Werner, > > this behaviour is normal because the smbpasswd file contains passwords > that are encrypted in the Windows style. And Windows doesn't differ between > upper and lower case (passwords and usernames). > > MfG PMD > > > > ----- Original Message ----- > From: "werner maes" <werner.maes@cc.kuleuven.ac.be> > Newsgroups: comp.protocols.smb,linux.samba > To: <samba@samba.org> > Sent: Wednesday, January 31, 2001 5:59 PM > Subject: Smbpasswd and Mixed-case passwords > > > >> Hello, >> >> Apparently the smbpasswd file doesn't care about mixed-case passwords. >> I've entered smbpasswd and changed my password to: MaEs. >> Then I did: smbclient //server/share -U werner and provided the wright >> password: MaEs. I managed to get access. >> BUT when I entered "maes" as password, it also worked. Same story with >> MAEs. >> >> Same story in Windows. >> Can anyone confirm this issue? >> >> Thanks alot, >> >> Werner Maes >> LUDIT-KULeuven >> >>
This is true for generating LanMan hashes, but not the NT hash (MD4 hash of the UNICODE password). I need to look as I thought smbclient was using the NT hash. Do you already which hash smbclient is using? Werner
werner maes wrote:> > This is true for generating LanMan hashes, but not > the NT hash (MD4 hash of the UNICODE password). > I need to look as I thought smbclient was using > the NT hash. > > Do you already which hash smbclient is using?If the negotiated protocol is < NT1 then only the LanMan hash is used. If NT1 is negotiated, then the smbclient includes the 24 bytes response for both the LanMan and NT hashes. Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
werner maes wrote:> > Hello, > > Apparently the smbpasswd file doesn't care about > mixed-case passwords. I've entered smbpasswd and > changed my password to: MaEs. Then I did: > smbclient //server/share -U werner and provided the wright > password: MaEs. I managed to get access. > BUT when I entered "maes" as password, it also > worked. Same story with MAEs.You will see this message in your smbd logs. NT Password did not match for user <username>' ! Defaulting to Lanman The reason your login succeeds is that smbclient sends both the LanMan and NT hash in the SMBsessetup request when the protocol negotiated is NT LANMAN 1.0. The LanMan hash is case insensitive due to the hashing algorithm so when the NT hash fails, Samba drops back to checking the LanMan hash. Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )