Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 31 Mar 2001 00:49:33 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: permissions Message-ID: <20010331004933.Z16622@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <002001c0b946$a757c3d0$c317a580@lanl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002001c0b946$a757c3d0$c317a580@lanl.gov>; from rick@lanl.gov on Fri, Mar 30, 2001 at 11:24:27AM -0700 On Fri, Mar 30, 2001 at 11:24:27AM -0700, Rick Rauenzahn wrote: > > I guess that ntsec makes all of the files in the cygwin tree have > permission rwx across the board. I gather this from reading the ntsec doesn't set that permissions. Switching ntsec on just show you what is really set by Windows as the default: Everyone has all permissions which is equivalent to POSIX perms rwxrwxrwx. > user's guide about ntsec. Is this desirable, or should I try to muck > with it, and set the permissions more like a Unix /usr tree? That's your choice! Except when playing with sshd, though. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple