Bug 433693 - Write only(dropbox) directories in shares do not allow access to when mounted using windows, Nautilus, or Mac OS X.
Summary: Write only(dropbox) directories in shares do not allow access to when mounted...
Keywords:
Status: CLOSED DUPLICATE of bug 497156
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: samba
Version: 5.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Guenther Deschner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-20 21:33 UTC by David Miller
Modified: 2010-04-26 14:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-26 14:40:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Miller 2008-02-20 21:33:25 UTC
Description of problem:
write only directories(other permissions set to write and execute only) do not
allow users to drag and drop items on them when mounted using a Windows client,
or mounted using nautilus under RHEL5, or mounted under a Mac OS X client.
Mounting the share using the mount.cifs in RHEL5.1 does allow for items to be
drag and dropped, using the mv or cp command, and also the touch command.

Version-Release number of selected component (if applicable):

3.0.25b-1.el5_1.4

How reproducible:

This is very easily reproducable.

Steps to Reproduce:
1. setup a samba share and at least one samba user account that can access the
share.
2. inside the share create a directory called dropbox. Give it the following
permissions. chmod go=wx ./dropbox
3. Connect to the share using a windows2000,XP, or Vista client.

4. drag and drop a simple text file on the dropbox directory.
  
Actual results:

an Error dialog saying access denied

Expected results:

File is copied into the dropbox directory

Additional info:

RHEL5 with samba version 3.0.23c-2 did not have this problem.

Comment 3 Dmitri Pal 2010-04-26 14:40:21 UTC

*** This bug has been marked as a duplicate of bug 497156 ***


Note You need to log in before you can comment on or make changes to this bug.