search for: dosattribs

Hi all, Is there a way to control the default DOS attributes stored in the user.DOSATTRIB value? I'm using a QNAP NAS device (running Samba) that seems to create files that have the 'hidden' DOS attribute set by the user.DOSATTRIB value as a default. The NAS device's smb.conf has the 'store dos attributes' option set to yes and each of the 'map hidden',

I have the following attributes for a typical file on my redirected folders residing on my Samba4 AD/DC: $ getfattr -d "Newletters/Newsletter 2013-09.docx" # file: Newletters/Newsletter 2013-09.docx user.DOSATTRIB=0sMHgyMAAAAwADAAAAEQAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPnD7jBHStABAAAAAAAAAAA= What do these characters mean? I'm searching for a particular attribute. I have found

...e "PnD7jBHStAB". Don't know if that's meaningful. Note also that doing getfattr from Linux on files from a mounted Windows C: drive I get nothing at all, even on %USERNAME%\Application Data, which I would think should have either 0x2 or 0x4. So maybe these Redirected Folder file DOSATTRIBs are a Samba thing? --Mark -----Original Message----- > From: "L.P.H. van Belle" <belle at bazuin.nl> > To: "samba at lists.samba.org" <samba at lists.samba.org> > Date: Wed, 26 Aug 2015 09:07:06 +0200 > Subject: Re: [Samba] Meaning of user.DOSATTRIB &gt...

Hi, I'm using Samba 3.0.24 in a LAN with Windows-only clients (Win2000/WinXP), and I've set it up to store DOS flags in extended attributes to make users happy: ea support = yes map archive = no map system = no map hidden = no store dos attributes = yes Now I was having a look at the current attributes in all my shared files, and was

Hai, This is al about samba ea ( extended attibutes ) support. Samba can map attibutes in two ways: Mapping DOS file attributes to UNIX permissions Storing the DOS attributes in extended file attributes The user.DOSATTRIB extended attribute contains a bit field indicating the state of each DOS attribute: Read-Only = 0x1 Hidden = 0x2 System = 0x4 Archive = 0x20 and in smb.conf related

https://bugzilla.samba.org/show_bug.cgi?id=5298 Summary: xattrs and acls do not work well together along with fake-super, even worse on XFS Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hello. I believe that I've done my due diligence in researching what info. is currently available on this issue. I have been jacking with this for days, & believe that I have tried all possible solutions. I am basically trying to move a [Merant] PVCS installation from an OS/2 file server to a SuSE/Samba file server. This installation consists of 'standard' source archives,

Samba 3.0.28-0.1.95-1624-SUSE-SL10.3 A strange problem (best read in a proportional font). It only happens on an x64 XP client when accessing a Samba share. The exact same program runs fine on the same x64 XP client when the share accessed is on a Windows server or when it is run on a 32-bit XP client, regardless of whether the share belongs to a Samba server or to a Windows server. I have

I cannot access home samba share from windows. Windows client displays a permission denied error. The problem is not Linux permissions for the user directory, permission is still denied when permissions are to 777. I don't think the problem is selinux, because no denials appear in any logs. I don't think it's an extended attributes issue from xfs, because I don't see any attributes

On Tue, 29 Aug 2023 15:44:35 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! Rowland Penny via samba > In chel di` si favelave... > > >> In samba the share is: > > I wish people wouldn't do this, if you are going to post a share, > > please post the global section as well. > > Sorry. > > # Global parameters >

Hi, I have a question regarding permissions at the top of a share as seen from a Windows 10 client. We are using Samba 4.10.6-Debian (van Belle) on Debian 10 (Buster) with one AD controller and one file server. The top directory of our main share on the file server has, on the Linux level, these permissions reported by getfacl: # file: ... # owner: root # group: domain\040users # flags: ---

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

I used setenforce 0, and I was extremely surprised to see a burst of selinux denials appear in the journal. So I corrected the problem with: setsebool -P use_samba_home_dirs 1 And updating some policies. Thanks very much! I have never before dealt with selinux denials that don't appear in the journal until "enforcing" is changed to "permissive". Is this a samba

Am 2019-08-26 um 16:35 schrieb Rowland penny via samba: > On 26/08/2019 15:20, ? Peter Rindfuss via samba wrote: >> Hi, >> >> I have a question regarding permissions at the top of a share as seen >> from a Windows 10 client. >> >> We are using Samba 4.10.6-Debian (van Belle) on Debian 10 (Buster) with >> one AD controller and one file server. >>

Everyone, I have finally resolved the new heartburn 3.0.24 on Ubuntu Feisty was giving me and have stumbled upon some information that might help others out there. I was seeing problems with ACL entries getting mangled and disappearing, Excel making files read only and extended attributes doing bizarre things. The solution revolved around what appears to be a change in how ACLs are managed.

I am following this guide https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs But hitting issues with setting permissions on the share in Computer Management in the windows AD DC UI. Every time I try I get the error dialog with +----------------------------------------------------------------+ | An error occurred while applying security information to | |

Since we use Samba 3.0.5 on Linux 2.6 with xattr and acl on ext3 I'm not longer able to set file attributes. In detail, I'm able fine because they are saved as the EA user.DOSATTRIB at the file. But the other part of Samba didn't know that and uses the normal mapping for reading the attributes resulting in no change of them. So I'm unable to mark a file e.g. read only. ea support

Hi, My Samba 3.6.6 file server isn't setting the security.NTACL extended attribute. It can set the user.DOSATTRIB without any issue. This appears to be an LXC container issue, as outside the container I can set this using the setfattr command without issue, whereas I can't do this inside. Despite this not being a Samba issue, I was wondering whether anybody has any encountered

In order to veriify if it is indeed SELINUX, what happens when you use 'setenforce 0' ? Usuallh , you need use_samba_home_dirs boolean to be enabled. Best Regards, Strahil Nikolov ?? 6 ??? 2020 ?. 19:31:46 GMT+03:00, Deft Developer via samba <samba at lists.samba.org> ??????: >I cannot access home samba share from windows. Windows client displays >a >permission denied

[ Received no feedback, i resend it... ] A little strange things, but i'm hitting my head on the wall... I needed to 'enlarge' my main filesystem (XFS backed-up), that contain my main samba share and a brick for a GFS share; i've setup a new volume (for the VM), formatted XFS, move all the file taking care to umount and stop GFS (so, syncing the brick, not the GFS filesystem)