similar to: Samba and ACL's

Hello, I am running Fedora Core 2. Kernel: linux-2.6.5-1.358 Kernel supports ACL: [root@atlas configs]# grep FS_SECURITY kernel-2.6.5-i686-smp.config CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT3_FS_SECURITY=y CONFIG_XFS_SECURITY=y CONFIG_DEVPTS_FS_SECURITY=y [root@atlas configs]# grep XATTR kernel-2.6.5-i686-smp.config CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS_XATTR=y CONFIG_DEVPTS_FS_XATTR=y Have

Hi I want to set Security to single file, but I keep getting access denied, I can change the Permissions that is alreday displayed, but I can add any user or group, after redaing the samba how to it seems I need POSIX ACL, but the book didn't mention anything about how to use POSIX ACL, Trying to set it from windows doesn't work, can anyone point me to document about POSIX ACL ? BTW

Extract of smb.conf : valid users (S) This is a list of users that should be allowed to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the invalid users parameter. If this is empty (the default) then any user can login. If a username is in both this list and the invalid

Hey, I refer to https://wiki.samba.org/index.php/Operating_system_requirements/File_system_support#ext4 Wiki suggests: Ensure that your kernel has the following options enabled: CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_SECURITY=y CONFIG_EXT4_FS_POSIX_ACL=y My debian 8.2 installation was installed from netinstall CD, all updates applied. All my filesystems are ext4 and xattr and acl are not set,

Hi, I have a problem with my Samba/WinBIND implementation. In folders shared by multiple people the last one to access and modify a file takes ownership of the file and changes the permissions so other users cannot make changes to the same file: [root@atlas PLANNING RECORDS]# cd REGIONAL\ 1\ AIRLINE\ DOCS/ [root@atlas REGIONAL 1 AIRLINE DOCS]# ls -al total 1232 drwxrws---+ 8 root

> On 29 Jul 2015, at 10:02, Ralph Böhme <rb at sernet.de> wrote: > Hm, works for me: > > mac$ mount | grep smb > //ralph at 10.10.11.100 <mailto:ralph at 10.10.11.100>/AAPL on /Volumes/AAPL (smbfs, nodev, nosuid, mounted by ralph) > mac$ touch /Volumes/AAPL/test > mac$ xattr -w foo bar /Volumes/AAPL/test > mac$ xattr -l /Volumes/AAPL/test > foo: bar >

> > I am not sure how to use Microsoft AD tools to create shares and then > set > those shares permissable to certain AD groups. For example, I need to > create > a share called "Finance" and only the people in Finance can read/write > to > it. I was hoping to use SWAT to help in creation and management of > those > shares. vi smb.conf (or your favorite

Hi, I am using kernel 3.7-rc6. I have written a test application for extended attributes and have for some folders a wired behaviour: #include <stdio.h> #include <string.h> #include <attr/xattr.h> char attrs[1024]; ssize_t attrslen; int i; char value[1024]; ssize_t valuelen; int main(int argc, char *argv[]) { if (argc != 2) { fprintf(stderr, "Syntax: testxattr

Currently, when listing xattrs, kernel define XATTR_LIST_MAX as 65536 in include/linux/limits.h, so it can't handle too many xattrs. But with ocfs2 xattr tree, we actually have no limit for the number. And it will pollute the message with something like this when listing. (27738,0):ocfs2_iterate_xattr_buckets:3158 ERROR: status = -34 (27738,0):ocfs2_xattr_tree_list_index_block:3264 ERROR:

https://bugzilla.samba.org/show_bug.cgi?id=6590 Summary: [sender] could not find xattr #1 for home/jdoe/TheFresh Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: stlman at

Hello, Often people (or applications) want to store additional information about a file. E.g. history, approval state, search tags, etc. Some file formats offer to integrate these metadata, some not (e.g. exif- headers, id3, etc.). My idea would be to create an additional <filename.xyz>.meta file next to a <filename.xyz> in the same folder. If the <filename.xyz> gets

Hello I am trying to integrate OS X 10.10.4 clients into existing Samba infractructure run by our IT department. We are currently using Samba 4.2.3. File share is stored on iSCSI array with ext4 filesystem which should support both ACL and XATTR. We are trying to setup vfs_fruit module to avoid possible performance problems on OS X clients. We do NOT user netatalk. Current vfs_fruit config:

My samba shares aren't working with ACL access since the upgrade. Here is an example of the error from /var/log/messages Dec 14 12:44:17 gfm-atlas smbd[14365]: [2006/12/14 12:44:17, 0] smbd/service.c:make_connection_snum(911) Dec 14 12:44:17 gfm-atlas smbd[14365]: '/usr/GFM_Shares/Users/Receiving' does not exist or permission denied when connecting to [GF_Receiving] Error was

Hi Rowland, >From the top down, I'm going to try and cover every step involved in the wiki and give you as much info as I can in the hope that we can get this issue resolved, or at least determine that there is nothing wrong with my config and that the underlying array has to be the weak point, even if none of us know why. *Step 1: Filesystem support* We need the filesystem to support

OK. Everything is going great for 4 years on my FC3 Samba Version 3.0.3-5. Now all of a sudden, when someone opens a Word/Excel file on a Samba share, it changes the user Owner to that user as well as modifies the permissions to r-x and leaves the group/permission bits/owner setting alone. I have the root directories for all shares with the u and g sticky bits set on, but it is not enforcing

Has anyone seen this when they do a getfacl on a samba share? [root@gfm-atlas GFM_Shares]# getfacl Installpoint/ # file: Installpoint # owner: root # group: AVMAX+domainadmins user::rwx group::rwx group:AVMAX+domain\040users:r-x mask::rwx other::--- default:user::rwx default:group::rwx default:group:AVMAX+domain\040users:r-x default:mask::rwx default:other::--- Notice the

Hi, I have Samba up and running as well as winbind. I have ran some tests to confirm that yes indeed winbind is able to query the Windows NT 4.0 PDC for user/group/password information. However I am having difficulty understanding how to set shares up in samba so that I can apply permissions to them using my Windows user information rather than creating each user on samba with the same password

Can I use a command like this to clone an NT ACL? getfattr -n security.NTACL templateFile | sed -e 's/templateFile/realFile/' | sudo setfattr --restore=- I can see that the attribute gets copied over but when I view the ACL in Windows security tab it's not the same ACL, it's much bigger and includes all kinds of default-like stuff. I'm trying to find a way to update

Hi, I am trying to understand how the extended attribute trusted.io-stats-dump works. setfattr -n trusted.io-stats-dump -v /tmp/gluster_perf_stats/io-stats-pre.txt /mnt/gluster/gv0_glusterfs I can see that the io-stats-pre.txt is created. But how and what happened in the background? And why I can't I see the attribute with getfattr again? getfattr -dm- /mnt/gluster/gv0_glusterfs # file:

>From samba 3.3.0 release notes, it seems like samba 3.3.x is at least experimenting using xattr to store NT ACL, which can eventually provide better NT ACL support. I tried similar features with samba 4.0.0 alpha6, which works very nice. Is there any plan to provide same level of NT ACL support with samba 3.3.x? If there is such plan, any targeted date for that? Thanks, Ying