X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=FFE9hqAuC9UGcBRi
	HfMcRNHfxeJup1Rp1HgNsblQQ/HUtcNKKzb1r4yvT941FEAvp7SlGsuHgH/KGDOR
	qdS6Q0TkOu2mT2ntiDxz9N1koR8u6udPX4YlQXH7CP/FcU8nm5vkhmLHh0CBIsvM
	GqVBzJXrTaCm8Zm94We/3yabTXM=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=o1BaR0kG+o+s/4kyk08o9Q
	GWy40=; b=JbpnLOsKx819wuArud2FhEQ6BGL9eOLmugCUvYNoNicpLeKhC3HxT8
	CGnHqeQB8nDGCa1odmLYaEkjaqbaUXWqeQ5a9bbcW8jkRDpvlF4Q/m65CQGMAv26
	k7sg1zjGAU2l63IYk2wuv9ydC4JGbMYlSwe0GBwAbUisZprgJ2X8M=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=4.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Fri, 7 Feb 2014 16:49:18 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	Andrey Repin <cygwin AT cygwin DOT com>
Message-ID:	<449939081.20140207164918@mtu-net.ru>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Subject:	Re: get rid of getpwent? (Was: cygwin-1.7.28 getpwent header declaration changes ?)
In-Reply-To:	<20140207094917.GN2821@calimero.vinschen.de>
References:	<52F339CA DOT 5070305 AT gmail DOT com> <20140206090117 DOT GD2821 AT calimero DOT vinschen DOT de> <52F361C5 DOT 3000807 AT gmail DOT com> <20140206141321 DOT GI2821 AT calimero DOT vinschen DOT de> <52F40208 DOT 5030901 AT etr-usa DOT com> <20140207094917 DOT GN2821 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Corinna Vinschen!

>> In some of these systems, you can edit /etc/foo and run a command to
>> manually sync that content back to the "real" user info DB.  (e.g.
>> the BSDs)  In others, direct edits to these files are ignored, but
>> the OS syncs a subset of changes to the user info DB to these files,
>> for the benefit of getpwent() and friends.  (e.g. Mac OS X.)

> That won't make much sense on Cygwin.  The idea is to use the existing
> OS tools to maintain the user/group databases in the first place.
> Having said that, it would, of course, be possible to implement Cygwin
> command line tools along the lines of useradd/usermod/groupdel.  For AD,
> they would just have to use LDAP, as Cygwin will do to read the account
> info.  It's pretty simple, as far as you view LDAP as simple,

LDAP IS simple. It's a shame it is so little known outside specific circles.

> However, I found that one functionality has to go completely.  It will
> not be possible anymore to ssh into your machine and add yourself to
> arbitrary groups by adding your user name to groups in /etc/group.  This
> is just not feasible anymore.

Erm. I call it a security improvement. To put it mildly.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 07.02.2014, <16:43>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -