Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
To: cygdev <cygwin-developers AT cygwin DOT com>
Subject: Re: NTSEC users: Please test
Reply-To: cygwin-developers AT cygwin DOT com
References: <20010716004416 DOT O25442 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Date: 25 Jul 2001 22:28:35 +0900
In-Reply-To: Corinna Vinschen's message of Mon, 16 Jul 2001 00:44:16 +0200
Message-ID: <s1sitgh9lz0.fsf@jaist.ac.jp>
Lines: 28
X-Mailer: Gnus v5.3/Emacs 19.34

>>> On Mon, 16 Jul 2001 00:44:16 +0200
>>> Corinna Vinschen <vinschen AT redhat DOT com> said:

> I think I found how to do it and I implemented it now that way:
> 
> - The DELETE permission is never used.
> - The FILE_DELETE_CHILD permission is only set on directories
>   if user (or group or others) has write and execute permission.
>   This reflects the POSIX permission to delete a file or subdirectory
>   only if w and x bits are both set.
> - If S_ISVTX bit should be set the FILE_DELETE_CHILD permission isn't
>   set for "others" even if they have write and execute bit set. This
>   seems to match the POSIX behaviour now as close as possible.

This way can't allow us to delete files created in the directory
with the special ACE, the full rights of the "creator owner".

The default temporary directory is C:/TEMP with the ACE on NT4.0.
The ACE is used to realize the semantics like the S_ISVTX bit on UNIX.
So we should be able to freely operate files created by ourselves
in the directory. But we can't delete them created by the new DLL.

I propose ntsec adds the DELETE permission of the owner to files
created in such directories.
____
  | AIST      Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
  | HOKURIKU  Center for Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology