Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: ntsec and NTFS inheritable permissions
References: <262990-220021028151721583 AT M2W072 DOT mail2web DOT com>
From: Roman Belenov <rbelenov AT yandex DOT ru>
Date: Wed, 09 Oct 2002 11:09:28 +0400
In-Reply-To: <262990-220021028151721583@M2W072.mail2web.com> ("lhall@pop.ma.ultranet.com"'s
 message of "Tue, 8 Oct 2002 11:17:21 -0400")
Message-ID: <u4rbwxf4n.fsf@yandex.ru>
Lines: 17
User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2
 (i386-msvc-nt5.1.2600)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Well, by groking I meant using them while deciding whether certain user
has access to file. And it seems that they are just ignored.

BTW Can you point me to this discussion in the list ? Searching list
archive I found only references to inheritable permissions problem
without description of the problem itself.

"lhall AT pop DOT ma DOT ultranet DOT com" <lhall AT pop DOT ma DOT ultranet DOT com> writes:

> I suppose it depends on what you mean when you say "cygwin doesn't
> grok inheritable permissions".  This email list has discussed in the
> past that Cygwin's permissions are "affected" by the setting of
> inheritable permissions in Windows.  There is no corollary in POSIX
> permissions, which is the view that Cygwin takes and enforces.

-- 
 							With regards, Roman.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/