Bug 128683
Summary: | Samba 3.0.4-6.3E breaks "Valid users" share definition access control method | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Tom Sightler <ttsig> |
Component: | samba | Assignee: | Simo Sorce <ssorce> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | samba-bugs-list |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:22:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Sightler
2004-07-27 22:12:14 UTC
I've checked this against the stock Samba distribution and it appears to be a change in bahaviour between 3.0.2 and 3.0.3. Since I can reproduce it with stock code I will probably file a bug with the Samba team as well. One noted difference in the log files, most of the users in the "transfer" group are winbind mapped users and we use the "winbind use default domain" option. With 3.0.2 it would check their name against the group as "testuser" but with 3.0.3+ it checks it as "DOMAIN\testuser" which is certainly a major behaviour change, however, adding the users to the group with this combined name still doesn't solve the problem however. Tom This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |