summaryrefslogtreecommitdiff
path: root/source3/libsmb/climessage.c
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2007-06-17 19:23:32 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 12:23:26 -0500
commita4354d399d65e0b0e660b0e41647c0116d51bd37 (patch)
tree80cf28285c6cb9b990cc837ac32db41b0a9063b1 /source3/libsmb/climessage.c
parent5e8a4c12f9617d7e7b2c392eddc1ced613a561fe (diff)
downloadsamba-a4354d399d65e0b0e660b0e41647c0116d51bd37.tar.gz
samba-a4354d399d65e0b0e660b0e41647c0116d51bd37.tar.bz2
samba-a4354d399d65e0b0e660b0e41647c0116d51bd37.zip
r23530: Fix bugs #4678 and #4697 which had the same root cause.
In make_server_info_pw() we assign a user SID in our authoritative SAM, even though this may be from a pure "Unix User" that doesn't exist in the SAM. This causes lookups on "[in]valid users" to fail as they will lookup this name as a "Unix User" SID to check against the user token. Fix this by adding the "Unix User"\unix_username SID to the sid array. The correct fix should probably be changing the server_info->sam_account user SID to be a S-1-22 Unix SID, but this might break old configs where plaintext passwords were used with no SAM backend. Jeremy (This used to be commit 80d1da7e6cce451d3934751feaa6ad60a337e3db)
Diffstat (limited to 'source3/libsmb/climessage.c')
0 files changed, 0 insertions, 0 deletions