just thought I would throw it out there.
-Original Message-
From: Tris Mabbs [mailto:tm-samba201...@firstgrade.co.uk]
Sent: 06 September 2013 13:01
To: Burgess, Adam
Cc: samba@lists.samba.org
Subject: RE: [Samba] primary GID based access for user in 16 supplementary
groups
Hiya
d.
Or at least that's how I understand it, and that's how it's worked
for me (I've got a couple of conversations going on at the moment, with some
extremely helpful Samba developers, regarding decoding Kerberos PACs in
particular ...).
Request membership and see wha
[mailto:tm-samba201...@firstgrade.co.uk]
Sent: 06 September 2013 10:15
To: Burgess, Adam
Cc: samba@lists.samba.org
Subject: RE: [Samba] primary GID based access for user in 16 supplementary
groups
Hiya Adam,
> We have not seen any issue with primary group not matching
> file/directory
gro
ds to be so much traffic in here (asked by users and can be
answered by other users) that more complex technical questions can
occasionally get overlooked.
Hope that helps, and good luck!
Cheers,
Tris.
-Original Message-
From: Burgess, Adam [mailto:adam.burg...@hp.com]
Sent: 06 Se
request
0x20089 or 0x11 for example.
-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On
Behalf Of steve
Sent: 05 September 2013 20:24
To: samba@lists.samba.org
Subject: Re: [Samba] primary GID based access for user in 16 supplementary
-
From: Tris Mabbs [mailto:tm-samba201...@firstgrade.co.uk]
Sent: 05 September 2013 19:46
To: Burgess, Adam; samba@lists.samba.org
Subject: RE: [Samba] primary GID based access for user in 16 supplementary
groups
Hiya Adam,
We too have had no end of problems with this sort of issue using Samba on
ur. Same UID,
different SID, never the 'twain shall meet ...
Hopefully at least some of that may prove useful!
Cheers,
Tris Mabbs.
-Original Message-
From: Burgess, Adam [mailto:adam.burg...@hp.com]
Sent: 05 September 2013 17:02
To: samba@lists.samba.org
Subject: [Samba] primary
We observe a difference between a Windows 7 client and Windows 2003/XP client
when accessing directories that should be accessible via the UNIX accounts
primary group GID. Windows client refuses access.
Ignoring for now why the two different client behaviours (either some subtle
difference in
On Thu, 2013-09-05 at 19:45 +0100, Tris Mabbs wrote:
> 5. Are you *absolutely* sure that your idmap back-ends are doing what you
> thought?
Here's another few cents:
What you are describing is almost certainly mismatched gidNumbers.
Depending on where the SID to GID mapping came from it will be