Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: ntsec and NTFS inheritable permissions References: <262990-220021028151721583@M2W072.mail2web.com> From: Roman Belenov 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: 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@pop.ma.ultranet.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/