Project

General

Profile

Feature #4714

Checkbox for "acl allow execute always" CIFS Option

Added by Ilya Koskin over 6 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
John Hixson
Category:
OS
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

On samba execution files in windows directly from share worked well even if you don't have "x" permissions.
On samba 4 you must have x permissions to run files. It is not comfortable.

On samba 4.1 there is new option "acl allow execute always" made for fixing this.

Adding "acl allow execute always = true" to axiliary parameters on CIFS options does the trick, but enabling it with checkbox
can be much more comfortable. And can be usefull for novice, who didn't know about this new samba feature.

Release announcement for samba 4.1 with that option: https://ftp.samba.org/pub/samba/rc/WHATSNEW-4.1.0rc4.txt

Associated revisions

Revision 64dfea12 (diff)
Added by John Hixson over 6 years ago

Set 'acl allow execute always = true' as the default - make it an option in the gui - reproduces samba3 behavior - give max open files breathing room Ticket: #4714

Revision 842f18fb (diff)
Added by John Hixson over 6 years ago

Set 'acl allow execute always = true' as the default - make it an option in the gui - reproduces samba3 behavior - give max open files breathing room Ticket: #4714

History

#1 Updated by John Hixson over 6 years ago

  • Status changed from Unscreened to Closed: Not To Be Fixed

Ilya Koskin wrote:

On samba execution files in windows directly from share worked well even if you don't have "x" permissions.
On samba 4 you must have x permissions to run files. It is not comfortable.

On samba 4.1 there is new option "acl allow execute always" made for fixing this.

Adding "acl allow execute always = true" to axiliary parameters on CIFS options does the trick, but enabling it with checkbox
can be much more comfortable. And can be usefull for novice, who didn't know about this new samba feature.

Release announcement for samba 4.1 with that option: https://ftp.samba.org/pub/samba/rc/WHATSNEW-4.1.0rc4.txt

I'm torn on what do to here ;-)

The man page for smb.conf also says this about this setting:

"This setting is not meant to be used as a permanent setting, but as a temporary relief:
It is recommended to fix the permissions in the ACLs and reset this
parameter to the default after a certain transition period."

I'm inclined to not put it in, and for those people who want to use it, it's certainly doable as an auxiliary parameter still. I think the proper fix is as suggested in the man page for the setting. It will go away in the future anyway. The "correct" way to fix this is to fix permissions.

#2 Updated by John Hixson over 6 years ago

  • Status changed from Closed: Not To Be Fixed to Resolved

I've went ahead and added this functionality in 64dfea12d309379d9ab87a77165e08ca74307871.

#3 Updated by Cyber Jock over 6 years ago

I just wanted to say "thanks" for fixing this John. This has been a thorn for many people in the forum. Just 30 minutes ago someone complained about the exact problem solved by this ticket. I let the forum user know that 9.2.1.4 has this fixed.

While I agree the proper fix is to fix the permissions, I think this is a very good choice for the majority of users.

#4 Updated by Plamen Kolev over 5 years ago

The problem still persists in FreeNAS-9.2.1-RELEASE-x64.

#5 Updated by Jordan Hubbard over 5 years ago

Probably not fixed in 9.2.1-RELEASE. Please upgrade to something newer. :)

#6 Updated by Dru Lavigne almost 3 years ago

  • Target version set to Master - FreeNAS Nightlies

Also available in: Atom PDF