Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Fri, 28 Feb 2003 11:45:19 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: cygwin=ntsec:[no]strict
Message-ID: <20030228164519.GA9304@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0302280950290 DOT 25599-100000 AT slinky DOT cs DOT nyu DOT edu> <3E5F7B1D DOT 935B69A7 AT ieee DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E5F7B1D.935B69A7@ieee.org>
User-Agent: Mutt/1.5.1i

On Fri, Feb 28, 2003 at 10:07:09AM -0500, Pierre A. Humblet wrote:
>Igor Pechtchanski wrote:
>>What about the "mkpasswd/mkgroup" group name?
>>
>Ditto, it should never occur anymore, except on user misbehavior or
>some really unexpected events (or existing incomplete files).
>
>When people seem to have ntsec problems on the list we should always
>ask for the output of id as well as cygcheck.  Things to watch for are
>the group name and whether the primary gid appears in the list of
>groups.

Should we have cygcheck run 'id'?

cgf