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:message-id:from:to:subject:references
	:in-reply-to:content-type; q=dns; s=default; b=sOGXMiit28FO6eHeU
	gzqEQYAslNjHAtrw/P7+B2LdhaN+cGZTvFGVkjaQQhy8aeX3Gc5VDs9mq0cE8PpL
	UiKPFlLxdwRrfm5AoEIpxKBjUTtZOudV+zDs+rRACuflbzSXGSupZTttphEM3EeX
	aZSVFQvtCLxQY57iNnk419bkWA=
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:message-id:from:to:subject:references
	:in-reply-to:content-type; s=default; bh=cIRubkTfDYCxqj3Rx0vzFeX
	FTNQ=; b=YfS20T2mJRcnnPltaM5+OIevl57/PcRYg4bkVktle7d+o+GPAz8EDe/
	8TuuVy9ymiKDzr307BDNTO5hoOiQosAswarqi5dH+y5cpAsOpUGZ4DBNDm666p47
	fP0FkjBb6V5F/WpzW0LawJTytZNZifcTSwisIDQfHKsXwtLVjUiw=
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=-1.6 required=5.0 tests=AWL,BAYES_00,PLING_QUERY,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=angle, replied, manner, H*f:sk:28f7eea
X-HELO: lb3-smtp-cloud2.xs4all.net
Date: Wed, 31 May 2017 16:16:38 +0200
Message-ID: <353243559c68bf1200675e2dc13c3d93@smtp-cloud2.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
To: cygwin AT cygwin DOT com
Subject: Re: openssh: privilege separation no longer supported on Cygwin? SURPRISE!
References: <d436698bbd53eef3cbdda788d4926109 AT xs4all DOT nl> <37b863f6-ce5c-ef13-569f-8044fe485075 AT gmail DOT com> <20e2702ca3837f5d54c558f8e786c717 AT xs4all DOT nl> <b16023ad6735108510ae351a8378a420 AT xs4all DOT nl> <262615c8cf6e134cedf97b0280c4a68f AT smtp-cloud2 DOT xs4all DOT net> <592E1C49 DOT 6020202 AT cygwin DOT com> <38be07babbfc69d5ccea67afe6f92794 AT smtp-cloud2 DOT xs4all DOT net> <28f7eeae-ed40-9837-53bc-d2d6a33ad5a7 AT gmail DOT com>
In-Reply-to: <28f7eeae-ed40-9837-53bc-d2d6a33ad5a7@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

On Wed, 31 May 2017 09:27:02, cyg Simple wrote:

[snip]
> All of this talk of /etc/passwd leads me to point you to
> https://cygwin.com/cygwin-ug-net/ntsec.html.

cyg,

Do you want me to study that text a second, third, fourth or Xth time ...?

However, let me take another angle now ...

Active Directory is just Microsoft's version of the 'network database', a way
to keep housekeeping in a centralized manner (like NIS).

Agreed?

Anyone out there, who uses AD, in stead of /etc/{passwd,group}, and observes
that the grandchild of the listener is executed by user "sshd"?

Anyone out there, who uses AD, in stead of /etc/{passwd,group}, and is brave
enough to delete the sshd account? Is ssh still working?

Now you might say that I am "a bit aggressive" above (yes, I _do_ feel a bit
peevish). However I would like to see arguments that stick and/or proof that
shows me wrong.

Larry Hall replied with an argument, you did not (neither did Andrey Repin).

Regards,

Henri


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