Bug 910735
Summary: | force user in smb.conf stopped working after update to 4.0.3 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Howarth <paul> |
Component: | samba | Assignee: | Guenther Deschner <gdeschner> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | abokovoy, asn, gdeschner, jlayton, ngaywood, sbose, ssorce |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-26 14:45:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul Howarth
2013-02-13 12:29:28 UTC
I have this same problem with samba-4.0.2-1.fc18.x86_64 After downgrading back to samba-4.0.1-1.fc18.x86_64 my "force user" shares started working again. I did not try 4.0.3 4.0.2 was security release, as well as 4.0.1, and both did not touch this part of the smbd. We need to look what additional patches were in 4.0.2-1 package compared to 4.0.1-1. This rules out any changes from upstream except, possibly, https://bugzilla.samba.org/show_bug.cgi?id=9518 I've been able to reproduce this with a minimal configuration. Install samba 4.0.2 Edit smb.conf I changed: # diff smb.conf-orig smb.conf 89c89 < workgroup = MYGROUP --- > workgroup = UNE 110c110,112 < max log size = 50 --- > max log size = 500 > log level = 3 passdb:5 auth:10 winbind:2 > 123,124c125,126 < security = user < passdb backend = tdbsam --- > ; security = user > ; passdb backend = tdbsam 147c149 < ; security = domain --- > security = domain 235a238 > wins server = 129.180.3.55 320a324,332 > > [testshare] > path = /home/testshare > read only = no > browseable = yes > volume = Test Share > force user = testuser > valid users = ngaywood > net rpc join -U user systemctl enable smb.service nmb.service systemctl start smb.service nmb.service I then tried to connect to smb://servername/testshare and was prompted for username/domain/password put in the details for ngaywood and the connection failed. I then downgraded the samba: yum downgrade libsmbclient-4.0.1-1.fc18.x86_64.rpm libwbclient-4.0.1-1.fc18.x86_64.rpm samba-4.0.1-1.fc18.x86_64.rpm samba-client-4.0.1-1.fc18.x86_64.rpm samba-common-4.0.1-1.fc18.x86_64.rpm samba-libs-4.0.1-1.fc18.x86_64.rpm Tried to connect to smb://servername/testshare, entered details for ngaywood and connected. Could place files in testshare as ngaywood. The files written as user testuser. I've reported this upstream https://bugzilla.samba.org/show_bug.cgi?id=9661 So from the upstream bug report, this is simply a change of behaviour. To fix the problem you need to edit your smb.conf file and add the 'force user' username to the list of valid users for the share. All working fine for me with samba-4.0.3-2.fc18.x86_64 and the configuration changes. Are you fine if we close this as NOTABUG? Yes, the workaround of adding the "force user" username to the list of "valid users" works for me. |