Thanks for the pointer, that's just what I needed to get on the right track. With some more reading, I found this can be done in the GUI on a per share basis by adding extra options for the SMB/CFIS share and it doesn't require going to the CLI at all. Just add the options and apply.
create mask = 0670
force create mode = 0670
directory mask = 2770
force directory mode = 2770Bro, you're asking a question in the wrong forum. The problem is directly related to the April update of Windows 10 1803, where for security reasons, support for executing exe files from samba v1 was disabled.
What can you do here:
try to run this file in windows 8 compatibility mode, it helps (sometimes),
disable support for SMB 1.0 / CIFS Client in Windows components (be sure to reboot),
well, if we talk about OMV, add the line "server min protocol = SMB2" to the additional SMB options in OMV
I'm also having this issue and don't see a confirmed fix. In my case, I verified that SMB 1.0 is already disabled on Windows clients, yet new files created on an SMB share from a windows machine (that end in *.exe) are not executable on the share. This seems to be a posix permission issue, not an samba version issue.
Yes, my mistake. Found this out on my system. However it seems to be not that obvious as I did not find a documentation for this in the web. Only trial and error approach as I did. Maybe you can point me in the right direction.
Based on the tests on my system the executable bit is necessary on a ext4 smb share. Seems to be also confirmed by OP.
When looking at the file system on OMV, new files are created with the group executable bit not set (0660 instead of 0670 or 0770). If I change them from the Linux CLI to add execute (chmod g+x [file name]) then execute works fine from Windows, but obviously I don't want to have to change it from the CLI every time a windows machine adds a new executable file.
The OMV documentation indicates that shares are created with 2770, meaning that new files are created with 770, but that's not what I'm seeing when files are created from a windows system over smb. New files created from Windows over SMB are set to 660.
I want the default to be that files created from windows systems have the group execute bit set in linux (0670 or 0770), how can that be done in in OMV?
