summaryrefslogtreecommitdiff
path: root/source3/configure.in
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2006-02-17 19:07:58 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 11:10:12 -0500
commit671c0098f683510194ae672973b167c0532eeba8 (patch)
tree50df73ffcd2e1f87566fef3701fe18c7064e27dd /source3/configure.in
parenta2f2a1d9f8f02bf4a4ffb38cc35a92cda770e4f4 (diff)
downloadsamba-671c0098f683510194ae672973b167c0532eeba8.tar.gz
samba-671c0098f683510194ae672973b167c0532eeba8.tar.bz2
samba-671c0098f683510194ae672973b167c0532eeba8.zip
r13545: A patch which I think it's time has come. VOlker, we can talk about
this more but it gets around the primary group issue. * don't map a SID to a name from the group mapping code if the map doesn't have a valid gid. This is only an issue in a tdb setup * Always allow S-1-$DOMAIN-513 to resolve (just like Windows) * if we cannot resolve a users primary GID to a SID, then set it to S-1-$DOMAIN-513 * Ignore the primary group SID inside pdb_enum_group_memberships(). Only look at the Unix group membersip. Jeremy, this fixes a fresh install startup for smbd as far as my tests are concerned. (This used to be commit f79f4dc4c58a6172bf69d37469fdd8de05a812df)
Diffstat (limited to 'source3/configure.in')
0 files changed, 0 insertions, 0 deletions