search for: cifsacls

...case AD is down). All other user/group accounts are >= 1001 and come from the AD. Technically that line should probably be 1001-29999, but not sure if that would impact user 1001. The only user in my /etc/passwd is local:x:1000:1000:local,,,:/home/local:/bin/bash > > You are using 'cifsacls' and this calculates a 32 bit ID from the SID, > so it is unlikely your users are getting the same ID from Samba and > cifsacls, I get the feeling that you use one or the other, not both :-\ > Can you please expand on this, I am confused as to what you are suggesting.? If 'gete...

...id > > And then it's a samba/winbind problem. Not sure how this could be a Samba problem ? 'S-1-5-18' is SYSTEM and from the looks of it, neither cifs.idmap or winbind maps it on a Unix domain member (it does map on a Samba DC). It is hard to understand from the manpages, does cifsacls use the same ID's as Winbind, or does it calculate its own ? Rowland

On 9/24/20 12:10 PM, Rowland penny via samba wrote: > On 24/09/2020 16:58, Ken Bass via samba wrote: >> On 9/24/20 11:51 AM, Aur?lien Aptel wrote: >>> The request-keys config looks right. >>> >>> You can check if winbind is properly configured trying to map with the >>> winbind CLI client called wbinfo. For example: >>> >>> # wbinfo -i

We've had a number of changes since the last release, and we have some other upcoming kernel changes that might require corresponding cifs-utils changes. So it's probably as good a time as any for a new release. Highlights: + fix for a minor security issue that can corrupt the mtab + new getcifsacl/setcifsacl tools that allow you to fetch and set raw Windows ACLs via an xattr. + a

On 9/24/20 11:51 AM, Aur?lien Aptel wrote: > The request-keys config looks right. > > You can check if winbind is properly configured trying to map with the > winbind CLI client called wbinfo. For example: > > # wbinfo -i NUC\\administrator > NUC\administrator:*:20501:20514::/home/NUC/administrator:/bin/bash > ^^^^^ ^^^^^ > uid

...MAIN_MEMBER > > i have 'winbind use default domain = Yes ' enabled if that is what you > are getting at. OOOPs, missed it :-[ OK, you are using users & groups in the 1000-29999 range, why ? could it be that you have the same users in /etc/passwd and AD ? You are using 'cifsacls' and this calculates a 32 bit ID from the SID, so it is unlikely your users are getting the same ID from Samba and cifsacls, I get the feeling that you use one or the other, not both :-\ Rowland

On 9/25/20 5:14 AM, Aur?lien Aptel wrote: > Ken Bass via samba <samba at lists.samba.org> writes: >> Can you please expand on this, I am confused as to what you are >> suggesting.? If 'getent pass' works properly and shows no >> overlap/confusion, this seems to be related to cifsacl. > It's still hard to say at this point. > > cifs.idmap logs

On 9/24/20 8:53 AM, Aur?lien Aptel wrote: > Ken Bass via samba <samba at lists.samba.org> writes: >> I installed a new Ubuntu 20.4 LTS system (smbd 4.11.6) . Initially I >> tried using the SSSD and 'realm' to join the domain. Everything worked >> similar to my Centos 7 install and I thought I was finished. >> >> The one thing not working is? cifs

Ken Bass via samba <samba at lists.samba.org> writes: > Can you please expand on this, I am confused as to what you are > suggesting.? If 'getent pass' works properly and shows no > overlap/confusion, this seems to be related to cifsacl. It's still hard to say at this point. cifs.idmap logs messages in the syslog. Can you try mounting with cifsacl, then look at logs

Rowland penny via samba <samba at lists.samba.org> writes: > 'S-1-5-18' is SYSTEM and from the looks of it, neither cifs.idmap or > winbind maps it on a Unix domain member (it does map on a Samba DC). It > is hard to understand from the manpages, does cifsacls use the same ID's > as Winbind, or does it calculate its own ? * cifsacl is the mount option. * When passed, it makes cifs.ko call the userspace program cifs.idmap everytime it has to map a SID. * cifs.idmap has a winbind or sssd backend (dynamicly loaded librairies aka plugins). * The...

On 25/09/2020 17:15, Ken Bass via samba wrote: > On 9/25/20 5:14 AM, Aur?lien Aptel wrote: >> Ken Bass via samba <samba at lists.samba.org> writes: >>> Can you please expand on this, I am confused as to what you are >>> suggesting.? If 'getent pass' works properly and shows no >>> overlap/confusion, this seems to be related to cifsacl. >>

On 9/25/20 12:23 PM, Rowland penny via samba wrote: > On 25/09/2020 17:15, Ken Bass via samba wrote: >> On 9/25/20 5:14 AM, Aur?lien Aptel wrote: >>> Ken Bass via samba <samba at lists.samba.org> writes: >>>> Can you please expand on this, I am confused as to what you are >>>> suggesting.? If 'getent pass' works properly and shows no

Hello all, I am looking to implement winbind and samba-client (mount.cifs, actually) on a RHEL6 machine with the following properties: 1. Users will log in to the RHEL6 box using Active Directory (2008 R2) credentials (via winbind) 2. There will be a global (i.e. not mounted on a per-user basis) CIFS mount at /client_data which points to a CIFS share on a Windows Server 2012 R2

On 9/24/20 8:53 AM, Aur?lien Aptel wrote: > Ken Bass via samba <samba at lists.samba.org> writes: >> I installed a new Ubuntu 20.4 LTS system (smbd 4.11.6) . Initially I >> tried using the SSSD and 'realm' to join the domain. Everything worked >> similar to my Centos 7 install and I thought I was finished. >> >> The one thing not working is? cifs

I installed a new Ubuntu 20.4 LTS system (smbd 4.11.6) . Initially I tried using the SSSD and 'realm' to join the domain. Everything worked similar to my Centos 7 install and I thought I was finished. The one thing not working is? cifs shares showing the proper id mapping. Based on some online posts, including from Rowland, I got rid of SSSD and configured samba/winbind only. Lots of

Dear Samba experts, IO would like to ask for help with diagnose why my Samba version 4.7.0-git. 23.4e3f0fb9d15SUSE-oS13.3-x86_64 in openSUSE Tumbleweed can not authentificate me on Windows server 2003 domain in /etc/fstab I have working combination - smb version only vorks if set to 1.0 //192.168.1.131/shares /home/fodrek/shares cifs credentials=/home/fodrek/

hello, Le 23/10/2019 ? 12:45, Rowland penny via samba a ?crit?: > On 23/10/2019 10:51, nathalie ramat via samba wrote: >> Hello, >> >> I have an server ad? - everything seems ok >> I have a windows client and a linux client . The users must to >> connect on windows or on linux with the same home. >> >> when I join my client linux with the command net

Hi all. Several years ago, Linux's CIFS kernel driver has implemented two little-known options, "idsfromsid" and "modefromsid" for Unix permission emulation. When both options are enabled, the Unix file user, group, and permissions are stored as SMB ACL entries, and is translated from, to, and checked as Unix permissions by the Linux client itself, without server

Dear Mr. Cardon! Na štvrtok, 9. novembra 2017 18:29:03 CET Denis Cardon via samba napísali: > > > IO would like to ask for help with diagnose why my Samba version > > 4.7.0-git. > > 23.4e3f0fb9d15SUSE-oS13.3-x86_64 in openSUSE Tumbleweed can not > > authentificate me on Windows server 2003 domain > > > > in /etc/fstab I have working combination - smb

I passed by the changelog for the Linux CIFS Kernel Module at https://wiki.samba.org/index.php/LinuxCIFSKernel. The following two sections caught my attention: >> 4.19 Kernel (69 changesets, module version 2.13) >>Allow cifs.ko to be built with insecure dialects disabled (vers=1.0 and vers=2.0 not allowed). Add support for snapshot >> mounts (specifying "snapshot="