Bug 86 - "delete readonly" vs. "delete on close"
Summary: "delete readonly" vs. "delete on close"
Status: RESOLVED INVALID
Alias: None
Product: Samba 2.2
Classification: Unclassified
Component: File Services (show other bugs)
Version: 2.2.8a
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-18 22:39 UTC by Robert Dahlem
Modified: 2003-06-03 10:39 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Dahlem 2003-05-18 22:39:42 UTC 
The "delete on close" semantics in smbd/close.c do not check for "delete
readonly = no". 

To reproduce: Configure a share with "delete readonly = no". Client is XP.
Open a command line window, change to the share.

	echo Testing >testfile
	attrib +r testfile
	del testfile              -> Access denied

No open Windows Explorer and delete the file. Explorer asks back, but it will
happily delete the file although it's read only and thus should not be deletable.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2003-05-19 12:58:18 UTC 
jra is the delete-on-close king
Comment 2 Jeremy Allison 2003-06-03 10:39:03 UTC 
This is not a bug. I have just checked W2k ---> w2k and it works identially
with a readonly file. Samba is behaving as Windows does here.

Jeremy.