I posted my original question below to the samba-ntdom list but it seems
to be the wrong place to be discussing this problem so I'm moving my
follow-up to these lists.
Background...I used to be using smbpasswd and the "unix password
sync",
"password chat", and "password program" settings to keep my
smb passwords
and unix passwords in sync. This was working well in an earlier release
of 1.9.18 but one of the messages below indicates that this broke in
1.9.18p10. I didn't notice it was broken until recently when I started
using 2.0.0beta1 and so I thought that it was broken only in the 2.0.0
samba domain control code.
I wrote:
> I'm using samba-2.0.0beta1.
>
> When trying to change a password as a non-root user with smbpasswd I get
> the following message from smbpasswd:
>
> machine 127.0.0.1 rejected the password change: Error was : The specified
> password is invalid.
>
> and the following message in log.smb:
>
> [1998/11/20 14:36:49, 0] smbd/chgpasswd.c:check_oem_password(684)
> check_oem_password: incorrect password length (1780921600).
>
> Whoa! I didn't type that many characters in my password! :-)
>
> Is this a known problem? Is there a fix in a later alpha?
Replies and my responses below...
On Fri, 20 Nov 1998, Douglas K. Fischer wrote:
> I've run across the same problem in 1.9.18p10 (see postings to
> samba-technical and main samba lists). I'm still trying to figure out
> exactly what's happening here but it seems that either the client is
> passing a bad data string into SamOEMhash or something wierd is happening
> inside of SamOEMhash. Of course, it could be something else entirely, I am
> far from a Samba guru...
>
> Douglas
>
> ----------------------------------------------------------------------
> Douglas K. Fischer DFischer@Bridgewater.EDU (540) 828 - 5343
> Network Systems Engineer C. E. Shull Information Technology Center
> College Box 36 Bridgewater College Bridgewater, VA 22812
> ----------------------------------------------------------------------
On Fri, 20 Nov 1998, Carlos Henrique wrote:
>
> Have you "unix password sync = yes" in smb.conf file?
Yes. In fact, the unix password change is working fine but then the smb
password change fails, which means my unix and smb passwords are getting
out of sync, which is what "unix password sync" is supposed to avoid.
> Have you any limit for unix passwords?
Only the standard Solaris 2.5 password defaults which impose a minimum
password limit of 6 characters. But this isn't the problem since, as I
said, the unix password change (via the password chat) is working fine.
> If the answer is yes for these questions, it's the problem.
> Else... I don't know...(I have similar problem).
Thanks for the replies.
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
