Samba 2.2.pre3 vs. 1.9.18 with unknown users
marek at bmlv.gv.at
Thu Jan 10 00:11:04 GMT 2002
I'm having problems again - but at least they are changing :-)
Using NT4SP5 as client and using a self-written program which does
for Username and Password (trying maybe already established logon
credentials) and, if that fails for any reason, doing
WHERE user IS NOT EQUAL TO THE LOGGED-ON USER.
With Samba 1.9.18 (or something in that direction ;-) that worked as designed.
With Samba 2.2pre3 (current CVS snapshot) samba sends a
STATUS_LOGON_FAILURE (looked into the packet sniffed off the network).
1.9.18 sent a "bad password".
This seems to lead NT to the conclusion that the user could have been ok,
and resends the "old" username (which wasn't specified and was so taken as
the currently logged on user) instead of the given one - which doesn't
work, of course.
So there are some solutions:
- Changing my program.
I'm not sure how to change it, though - I'm using a documented behaviour.
And if I'm just eliminating the WNet(...,NULL,NULL,...) case I may get
problems if the user is already logged on with another user/password pair.
- Changing samba to return the "old" failure codes. That is, "bad password"
irrespective if the user and/or the password is wrong.
That's unclean, too.
So please give me advice what I can do to avoid this (in my opinion an NT-)
Thanks for all answers!
This message is RSA-encrypted: n=33389, e=257
More information about the samba-technical