Bug 125812

Summary: "force user" and "write list" do not work anymore
Product: [Fedora] Fedora Reporter: Markus Dobel <mdobel>
Component: sambaAssignee: Jay Fenlason <fenlason>
Status: CLOSED INSUFFICIENT_DATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1CC: jfeeney, mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-28 17:13:51 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 Markus Dobel 2004-06-11 19:07:28 UTC
From Bugzilla Helper:
User-Agent: Opera/7.50 (Windows NT 5.0; U)  [en]

Description of problem:
The following share:

[data]
        path                            = /home/data
        guest ok                        = no
        browseable                      = no
        read only                       = yes
        write list                      = @datarw
        directory mask                  = 0750
        create mask                     = 0640
        force user                      = data
        force group                     = datausers

should be: 
  inaccessible for "the world"
  readable by any valid user
  writeable by members of "datarw"

all users accessing this share are members of the group "datausers", 
the read/write users are members of "datarw", too. all files and 
directories in the share have the same permissions like defined in 
directory/create mask:

-rw-r-----   1 data datausers    444807 Feb  2 00:05 somefile
drwxr-x---   2 data datausers       392 May 20 11:02 somedirectory

This setup behaved as expected for years starting with redhat 6.x 
(and the corresponding samba version)up to fedora core 1 with 
samba-3.0.2-7.FC1.

in 3.0.4 it seems, that "force user" and/or "write list" is ignored, 
as the share is not writeable anymore.

Downgrade to 3.0.2 "fixed" the problem.


Version-Release number of selected component (if applicable):
samba-3.0.4-1.FC1

How reproducible:
Always

Steps to Reproduce:
1. Install samba-3.0.2 with security=user and the described share
2. Try to write to the share -> works
3. Upgrade to samba-3.0.4 -> no write access
    

Actual Results:  no write access to the share

Expected Results:  being able to write to the shared folder

Additional info:

Comment 1 Matthew Miller 2006-07-11 17:28:48 UTC
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.

Thanks!

NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.



Comment 2 John Thacker 2006-10-28 17:13:51 UTC
Note that FC1 and FC2 are no longer supported even by Fedora Legacy.  Many
changes have occurred since these older releases.  Please install a supported
version of Fedora Core and retest.  If this still occurs on FC3 or FC4, please
assign to that version and Fedora Legacy.  If it still occurs on FC5 or FC6,
please reopen and assign to the correct version.  Thanks!