search for: disable_us

...n the /etc/passwd file; thus pwd = null pointer. :) I'd supply a patch to fix this; but there are various ways to 'fix' this and not knowing enough about the protocol... web/swat.c: line 635 ret = local_password_change(user_name, False, add_user, enable_user, disable_user, False, new_passwd, err_str, sizeof(err_str), msg_str, sizeof(msg_str)); passdb/smbpasschange.c: line 58 BOOL local_password_change(char *user_name, BOOL trust_account, BOOL add_user, BOOL enable_user, BOOL disable_user, BOOL set_no_password, char *n...

...n the /etc/passwd file; thus pwd = null pointer. :) I'd supply a patch to fix this; but there are various ways to 'fix' this and not knowing enough about the protocol... web/swat.c: line 635 ret = local_password_change(user_name, False, add_user, enable_user, disable_user, False, new_passwd, err_str, sizeof(err_str), msg_str, sizeof(msg_str)); passdb/smbpasschange.c: line 58 BOOL local_password_change(char *user_name, BOOL trust_account, BOOL add_user, BOOL enable_user, BOOL disable_user, BOOL set_no_password, char *n...

...dle both Unix and Samba accounts. Specifically, smbldap-usermod has a "-I" option, which is described as "disable user". It sets the "D" flag on the Samba account info, but it doesn't have any effect on the RFC 2307 userPassword. I noticed smbldap_tools.pm has a disable_user() sub in it, which is even exported from the module, but nothing calls it, and when I tried calling it myself from a little Perl code, it didn't seem to work. Oh, and I can't really use the straightforward "passwd -l" command, because I'm using Slackware, which doesn't...