delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2003/02/28/10:04:40

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
Message-ID: <3E5F7B1D.935B69A7@ieee.org>
Date: Fri, 28 Feb 2003 10:07:09 -0500
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: cygwin=ntsec:[no]strict
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0302280950290 DOT 25599-100000 AT slinky DOT cs DOT nyu DOT edu>

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.

Pierre

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019