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:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=OPjcA0ln9/MhNPE3PFzi
	Ln65MHDAv7ZgCuyRefkRq/fRbtrXVEjWYjGrKyEUx3d/ZzP+hLeFqGV2yGB9esNN
	KPOZBptzNy279fKyKfmokjeppd+ETIhPvHeRhuriZpYO9ktcxXip6yjmSnyPhr3c
	MpcKSMnSSQI7+9N7Pgx7Q/U=
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:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; s=default; bh=A7cywtuf+WHHxZG6jrMvBi9aoY
	8=; b=blpy3kDo9USkQe172tuNtK6CNuiCL+KWAjYvIgjBiufJOd7tATQ1+mloUd
	ouioafadFIn4A2PTm9hMaTHQMiUoclXe2M7K7ZH0Nvt36AAtE+qdSt3GhbwRg/DE
	1dlU6nS47+3gjX45lJymbesLsbyy3wgEvybYgP5fbpEBvyQ8c=
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=H*f:sk:b16023a, H*F:D*nl, userid, surprise
X-HELO: lb3-smtp-cloud3.xs4all.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 29 May 2017 22:30:15 +0200
From: Houder <houder AT xs4all DOT nl>
To: cygwin AT cygwin DOT com
Subject: Re: openssh: privilege separation no longer supported on Cygwin? SURPRISE!
In-Reply-To: <522816658.20170529225714@yandex.ru>
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> <522816658 DOT 20170529225714 AT yandex DOT ru>
Message-ID: <eeafed231e0df1a879581f18e2067745@xs4all.nl>
X-Sender: houder AT xs4all DOT nl
User-Agent: XS4ALL Webmail
X-IsSubscribed: yes

On 2017-05-29 21:57, Andrey Repin wrote:
> Greetings, Houder!
> 
>>   - however, the userid of the grandchild of the sshd listener, is 
>> STILL
>>     cyg_server ... NOT sshd!
> 
> Exactly. cyg_server is the user which does impersonation.
> You've been told that when you've been setting up your host.

     http://www.citi.umich.edu/u/provos/ssh/privsep.html

     
https://security.stackexchange.com/questions/115896/can-someone-explain-how-sshd-does-privilege-separation

     https://cygwin.com/ml/cygwin/2017-05/msg00468.html

>> As if the "sshd" account is NEVER, NEVER used during the _whole_ 
>> process
>> (that is, there is NO privilege separation, as far as I can tell).
> 
> As far as it is documented.

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