Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sat, 24 Aug 2002 18:53:10 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <135198941843.20020824185310@logos-m.ru> To: "Pierre A. Humblet" CC: cygwin-developers AT cygwin DOT com Subject: Re: acl_access denies access owned by 'Everyone' group In-Reply-To: <3D6665E2.92F8C445@ieee.org> References: <19113724867 DOT 20020823191251 AT logos-m DOT ru> <3D6665E2 DOT 92F8C445 AT ieee DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Friday, 23 August, 2002 Pierre A. Humblet Pierre DOT Humblet AT ieee DOT org wrote: PAH> But I also believe your setup is non-sensical. It makes no sense to have a PAH> file in the Everyone group. Everyone is already used in the file ACL to PAH> record access rights for "other". If the group is Everyone, there is no PAH> way to distinguish between "group" rights and "other" rights. Note that PAH> as a side effect "other" is shown as having no access to the file. PAH> See my recent e-mail in the cygwin-patches list. PAH> Because of the impossibility to distinguish between "group" and "other" access PAH> in such a case, there is no way to handle the situation "correctly". Are you talking about nt->unix access rights mapping here? What if in this case we set permissions like this: -abcxyzxyz user Everyone file_name ? Or having file owned by 'Everyone' group has other side-effects? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19