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=sbip9WtzPRsV8OHN
	6x2fSYwBNShrlQtD1PVMawBAx8K/vXILvxSQOMkxHfV1tW0vHVLrDJPjxgAIHPNK
	qyOwOk78mfGw1JIztqyx6GVVpLiBE1iZp1wZAPjQDhTRNEhbk76QpEJbcehFADPC
	Nts+lMWGNEvaPeXJ9pxMFuhQatQ=
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=ushTF/WPmbp0IrWaje3OsS
	bKzoY=; b=P41Adp6rgkqAVhQzuRvNOeaLiQy1wonjQBEGkFj6KzdtbcnSGVEw2a
	Q0jxSfEWZG4SIav0CdlbcN4tePeQeRwuqEN3wSH8JXiFtIHk7KlJR9Gp8UGNG2Wf
	gOYfWy4mvoJ6bDatYeMp9BVQtFAAKfztHyYLzQBVnG6RCyat3+p+I=
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.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Tue, 21 Jul 2015 03:25:32 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1399485278.20150721032532@yandex.ru>
To: Jarek <yaro_29 AT hotmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Cygwin ssh and Windows authentication
In-Reply-To: <BLU436-SMTP217DCBDBFA0EED5BC1ACFFB9E850@phx.gbl>
References: <BLU436-SMTP39AE7DD48809E802CE4DAE9E860 AT phx DOT gbl>   <1301881165 DOT 20150720013859 AT yandex DOT ru>  <BLU436-SMTP217DCBDBFA0EED5BC1ACFFB9E850 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Jarek!

> So why are they not needed as your comment doesn't really explain that

Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain controllers for it.

> and how exactly did I screwed up my setup if I can actually access the 
> server with a domain user account no problem?

On that, I'm surprized.

> Perhaps it's not how it works but it somehow works so again would be good to
> know why. It's only domain groups that don't work. Even if I set the service
> account to run under a domain account how would this fix my problem with
> group access assuming in current setup it works for domain users but not for
> groups?

> Again if not the /etc/passwd or /etc/group files then what controls the 
> access?

/etc/passwd/group has nothing to do with "access control".
The files were only used to convert Windows to Cygwin names (and supply other
Cygwin-specific information), on the presumption that there will never be too
much of it. This is now done on the fly, allowing to deploy Cygwin in large
domains.

P.S.
I would appreciate, if you don't top-post.


-- 
With best regards,
Andrey Repin
Tuesday, July 21, 2015 03:02:14

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