On Wed, Jul 20, 2005 at 05:02:25PM +0300, Alexander Gattin wrote: > Package: smbfs > Version: 3.0.14a-3 > Severity: important
> I tried to do homedir automounting through CIFS > protocol. It's pretty obvious SMB isn't approproiate > for this task, although first I tried libpam-mount/SMB > and it worked. CIFS didn't. For the same account, of > course. > As it turned out the source of problem is difference in > password processing between mount.smbfs and mount.cifs. > It seems that the latter mistreats passwords containing > comma (as was in my case), and probably some other > non-alnum characters too. > 4. mount through CIFS at remote side: > >vespasian:~# mount.cifs //penguin/luser /mnt -o user=luser > >Password: luser,r > >mount error 13 = Permission denied > >Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) > 5. of course, I checked SAMBA logs: > >[2005/07/20 15:59:53, 3] libsmb/ntlm_check.c:ntlm_password_check(344) > > ntlm_password_check: NT MD4 password check failed for user luser > ... > >[2005/07/20 15:59:53, 5] auth/auth.c:check_ntlm_password(271) > > check_ntlm_password: sam authentication for user [luser] FAILED with > > error NT_STATUS_WRONG_PASSWORD > >[2005/07/20 15:59:53, 2] auth/auth.c:check_ntlm_password(312) > > check_ntlm_password: Authentication for user [luser] -> [luser] FAILED > > with error NT_STATUS_WRONG_PASSWORD > Here you can plain see that password used by mount.cifs > simply _doesn't_ _match_. I'm not convinced that this bug is as simple as you suggest it is. IIRC, the [luser] -> [luser] in Samba logs is username and mapped username, not username and password, so this doesn't really suggest a reason *why* the password was not accepted. Can you check this, by changing the password in your example so that the part before the comma is something *other* than the username? Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
