samba - Nov 2018 - Fileshare - how to enable Modify permission for an rwx-enabled file

Thank You, Rowland.

I have already read that. According to chapter File System Support, does
that imply, that Samba could also well never grant Modify permission for
linux ACLs? Do I need extended ACLs on filesystem in order to do that? I
thought, that write permission on filesystem should be sufficient for
Samba to grant Modify for Windows...

As of smb.conf, here is snippet

[pripomienkovanie]

   path = /mnt/data_disk/www/pripomienkovanie/
    dos filetime resolution = yes
    writable = yes
    read only = no

    preserve case = yes
    create mask = 775
    directory mask = 2775

    oplocks = false
    level2oplocks = false


Dňa 16. 11. 2018 o 11:28 Rowland Penny via samba
napísal(a):
> On Fri, 16 Nov 2018 10:03:08 +0100
> "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org>
wrote:
>
>> Hi,
>>
>> I'm searching the web for a while but cannot find an answer to
this,
>> even on Samba wiki, so please, does somebody have a clue, how to
>> enable MODIFY access permission for a file that is located on Samba
>> share?
>>
>> The fileserver is Samba, member of AD domain, local filesystem ext4,
>> basic ACLs. The file has properly set rwx for users and groups needed,
>> both for a file and for parent directory. However, for Windows 10 /
>> Windows 2016, the file Properties - Security tab reports only Read
&
>> Execute, Read, Write, Special permissions rights for the said
>> users/groups. The Modify permission is NOT SET. In effect, when the
>> user opens the file in Office app, he gets "file is read
only"
>> warning. OTOH, user can create new files in directory.
>>
>> We haven't had such problem with samba 4.2 fileserver, member of
NT4
>> domain.
>>
>> Has the ACL translation model changed since? Or what might be a
>> culprit? What should I do to make samba enable Modify permission for
>> RWX-enabled files?
>>
>>
>>
> Have you read this wiki page:
>
> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs
>
> It might also help if you post your smb.conf
>
> Rowland
>

On Fri, 16 Nov 2018 12:16:15 +0100
"Mgr. Peter Tuharsky via samba" <samba at lists.samba.org>
wrote:
> Thank You, Rowland.
> 
> I have already read that. According to chapter File System Support,
> does that imply, that Samba could also well never grant Modify
> permission for linux ACLs? Do I need extended ACLs on filesystem in
> order to do that? I thought, that write permission on filesystem
> should be sufficient for Samba to grant Modify for Windows...
Linux has nothing that compares to 'modify' directly, it has
'rwx' or
'read, write and enter/execute', for what you want, you need to use
Windows ACL's and these will be stored in an EA.
> 
> As of smb.conf, here is snippet
Posting parts of a smb.conf without the [global] section is like
posting just one page of a book, you do not get the full context ;-)
> 
> [pripomienkovanie]
> 
>    path = /mnt/data_disk/www/pripomienkovanie/
>     dos filetime resolution = yes
>     writable = yes
>     read only = no
The above two lines are interesting, if something is writable, this
means it isn't just readable, or to put it another way, they both mean
the same so why have both ?
> 
>     preserve case = yes
>     create mask = 775
>     directory mask = 2775
> 
>     oplocks = false
>     level2oplocks = false
Why don't you want oplocks ?

To be honest, I would replace all of the above with this:

[pripomienkovanie]
    path = /mnt/data_disk/www/pripomienkovanie/
    read only = no

Then follow the wikipage I point you to earlier.

Rowland

Thank You again, I'll give xattr a try again (last time I switched it
off because of problems).

Dňa 16. 11. 2018 o 12:42 Rowland Penny via samba
napísal(a):
> On Fri, 16 Nov 2018 12:16:15 +0100
> "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org>
wrote:
>
>> Thank You, Rowland.
>>
>> I have already read that. According to chapter File System Support,
>> does that imply, that Samba could also well never grant Modify
>> permission for linux ACLs? Do I need extended ACLs on filesystem in
>> order to do that? I thought, that write permission on filesystem
>> should be sufficient for Samba to grant Modify for Windows...
> Linux has nothing that compares to 'modify' directly, it has
'rwx' or
> 'read, write and enter/execute', for what you want, you need to use
> Windows ACL's and these will be stored in an EA.
>
>> As of smb.conf, here is snippet
> Posting parts of a smb.conf without the [global] section is like
> posting just one page of a book, you do not get the full context ;-)
>
>> [pripomienkovanie]
>>
>>    path = /mnt/data_disk/www/pripomienkovanie/
>>     dos filetime resolution = yes
>>     writable = yes
>>     read only = no
> The above two lines are interesting, if something is writable, this
> means it isn't just readable, or to put it another way, they both mean
> the same so why have both ?
>
>>     preserve case = yes
>>     create mask = 775
>>     directory mask = 2775
>>
>>     oplocks = false
>>     level2oplocks = false
> Why don't you want oplocks ?
>
> To be honest, I would replace all of the above with this:
>
> [pripomienkovanie]
>     path = /mnt/data_disk/www/pripomienkovanie/
>     read only = no
>
> Then follow the wikipage I point you to earlier.
>
> Rowland
>
>