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:message-id:date:from:mime-version:to:subject
	:in-reply-to:content-type:content-transfer-encoding; q=dns; s=
	default; b=kfgikvIQbtLzgiFSynNMrUtg3Ongu16K0ze9RMu59RQNgJ0ID/02H
	WnayXmLqUyA1cAsVk2xz9iJxU+St3u3JCujI1akd3zmq6xoMIHoIIKcax3/59xDe
	qMoqr/whJFWL6xihvBASr45trpSDC8TdelZXFdNvgM562qAVyEeka0=
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:message-id:date:from:mime-version:to:subject
	:in-reply-to:content-type:content-transfer-encoding; s=default;
	bh=2jo784HCfGmsXaMEZgDo5hqB/0c=; b=G0nbM64pEZ/3mI5ZIwAubTZqpYdI
	s7+ch/EtyiAaWlmF90V3HX2wrdPb4+hRTO2OEltzR2s+DF40OPwj8yyYMjJEk8f0
	GdvBA5lcDygYeUxyKkuUHg4K1L8TLGCevLyVU4CXf+r0Er6FDEkz714Jov+RXb3Y
	ZJNjkdVPz2rgJk0=
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=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ee0-f53.google.com
X-Received:	by 10.14.194.2 with SMTP id l2mr3886644een.39.1392320224638; Thu, 13 Feb 2014 11:37:04 -0800 (PST)
Message-ID:	<52FD1EDB.8060708@googlemail.com>
Date:	Thu, 13 Feb 2014 20:36:59 +0100
From:	m0viefreak <m0viefreak DOT cm AT googlemail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version:	1.0
To:	Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: Testers needed: New passwd/group handling in Cygwin
In-Reply-To:	<20140213143849.GH2246@calimero.vinschen.de>
X-IsSubscribed:	yes

Hello,

I have a a question about how this change is going to affect
third-party utilities. Especially in the case once chooses to
use the PAM method and get rid of any /etc/{passwd,group}
files completely.

There seem to be programs (mostly scripts) that make use of
/etc/passwd as a file directly.

One of them is for example "ssh-host-config".

The shell script:

- works with the file directly:
  ...
  run_service_as=$(/usr/bin/grep -Fi "${accnt_name}" /etc/passwd | /usr/bin/awk -F: '{print $1;}') 
  ...

  I assume this would have to be changed in the sshd package?

- After the script is run it sets various entries in the
  /etc/passwd file (sshd shell to /bin/false and home to /var/empty).
  I assume I would have to migrate these changes into the <cygwin />
  comment if I were to remove the passwd file now.
  But more importantly, if I were to run sshd-host-config with
  no passwd file present at all, would it correctly set up the
  <cygwin /> comment entry in the PAM?

Grepping through /bin I found at least one other package
that makes use of /etc/passwd as a file directly (cvsbug), but 
since I don't have everything installed I can only assume there
are more cygwin-packages and other programs someone might build
from source.


An idea that might sound a bit far-fetched: In case the above
is actually a problem, would it be possible to populate a virtual
/etc/passwd file on-the-fly the same way /dev/ and /proc/ are?
This way programs that rely on reading the passwd file direclty
would just keep working (writing would be more complicated
of course).


--
m0vie

--
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 -