Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 1 May 2000 17:03:33 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: ntsec doesn't work at all. Message-ID: <20000501170333.A8049@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <390DE90D DOT B31F3417 AT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <390DE90D.B31F3417@vinschen.de>; from corinna@vinschen.de on Mon, May 01, 2000 at 10:29:01PM +0200 On Mon, May 01, 2000 at 10:29:01PM +0200, Corinna Vinschen wrote: >Kazuhiro Fujieda wrote: >> >> ntsec doesn't work at all since the 2000/04/25 snapshot. >> >> According to the SDK documents, GetFileSecurity sets the value >> of the last argument to zero if it get security descriptors >> successfully. So read_sd() in security.cc always return 0. > >??? ntsec works ok. The SDK documentation is wrong. >GetFileSecurity returns the size of the SD. Just checked >it again. Is this an NT4.0/2000 issue? cgf