changing smbpasswd from the cmdline with 2b2

[Andy Bakun]

Something interesting.  For those of you playing along at home, I changed the
smbpasswd of a user, but got a password mismatch during setting it.  After this,
the account becomes unusable -- the password is apparently set to something
unrelated to the old password.  And the messages that smbpasswd prints in this
case are confusing.

Note that abakun's password was oringally set to 'original'.

jupiter:~# smbclient //jupiter/tmp -U abakun
Password: original
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.0.0beta2]
smb: \> quit
jupiter:~# smbpasswd abakun
New SMB password:abc
Retype new SMB password:xyz
Mismatch - password unchanged.
Password changed for user abakun
jupiter:~# smbclient //jupiter/tmp -U abakun
Password: abc
session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a
Tree Connect or Session Setup are invalid.)
jupiter:~# smbclient //jupiter/tmp -U abakun
Password: xyz
session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a
Tree Connect or Session Setup are invalid.)
jupiter:~# smbclient //jupiter/tmp -U abakun
Password: original
session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a
Tree Connect or Session Setup are invalid.)
jupiter:~# smbpasswd abakun
New SMB password:somethingnew
Retype new SMB password:somethingnew
Password changed for user abakun
jupiter:~# smbclient //jupiter/tmp -U abakun
Password: somethingnew
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.0.0beta2]
smb: \> quit

And the date on the private/smbpasswd file changes.  But the account is
unusable, as seen above.

Andy.