Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <36E98798.9B4168D1@cityweb.de>
Date: Fri, 12 Mar 1999 22:31:04 +0100
From: Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: Geoffrey Noer <noer AT cygnus DOT com>
CC: Sergey Okhapkin <sos AT prospect DOT com DOT ru>,
        "cygwin32-developers AT cygnus DOT com" <cygwin32-developers AT cygnus DOT com>
Subject: Re: Patch, Version 2: UNIX-like permissions on objects
References: <01BE6763 DOT 664406B0 AT sos> <36E8C558 DOT BC757DBE AT cityweb DOT de> <19990312121135 DOT A9190 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Geoffrey Noer wrote:
> 
> On Fri, Mar 12, 1999, Corinna Vinschen wrote:
> >
> > How would you like to get the information about the users
> > default shell???
> 
> Consider shadow passwd files on Unix.  The actual passwords are
> stored elsewhere; this is a little like what we're already doing
> with Cygwin in that the passwds are kept in the Windows OS.
> We can continue to use a physical /etc/passwd as an optional file to
> keep home directories and shells but have Cygwin handle the rest?
> If a user doesn't have an /etc/passwd entry, then slash would be
> their home and bash would be their default shell.
> 
> Opinions?

So, IMHO, we already (nearly) do, what should be done! The inetd
of the remote package already read NT password, the passwd utility
sets the password.
To read also comment and home directory from NT user database is
a trivial thing.
But the problem, from my point of view, is the attachment of a user
to the primary NT group.
Exists a useful solution for this problem anywhere???

Corinna