Univention Bugzilla – Full Text Bug Listing |
Summary: | Files on Samba 4.x shares not executable any longer without explicit "executable" permission | ||
---|---|---|---|
Product: | UCS | Reporter: | Arvid Requate <requate> |
Component: | Samba | Assignee: | Felix Botner <botner> |
Status: | CLOSED FIXED | QA Contact: | Arvid Requate <requate> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, walkenhorst |
Version: | UCS 3.2 | ||
Target Milestone: | UCS 3.2-2-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=33918 | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 35137 |
Description
Arvid Requate
2013-12-19 12:28:55 CET
2014050921003881 This is a quite invasive change to the behaviour between UCS 3.1 and UCS 3.2 that is not even mentioned in changelog/release notes. Just to make this clear: "Samba 3" setups are affected too! Workaround: -- /etc/samba/local.conf [global] acl allow execute always = True -- I think we should, at least, add a this to the release notes. Set to 3.2-2-errata otherwise it is out of my scope. Added samba/acl/allow/execute/always (default yes) to univention-samba to configure samba option "acl allow execute always" (global). YAML: 2014-06-17-univention-samba.yaml Ok, looks mostly good, for all four tests (s3,s4)x(master,backup,slave,member) it only failed once in the last 26 test runs. That singke failure was an authentication error during the test: http://jenkins.knut.univention.de:8080/job/UCS%203.2-2%20Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=slave/33/testReport/junit/10_ldap/74schema_update/test/ So verified for now. Oops, wrong bug.. ignore the last comment. Verified: * UCR variable is documented and set to yes on update * smb.conf template default is yes * A user logged on to a windows client can execute files without x-bit * setting the variable to no restores the old behaviour * Advisory ok |