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
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=X5PFnilR9y2z+UeLrK81h/XEFBPZ5Ri5dvOHc3iiHJ4
	nPv/izAmNnWqtI6AfMC/WGFm5H8zOgeihrdnwzot6GDFzpP1tERh9VjZnoeU3r6H
	d9sNvjO827kI0wyi52GaBE+BEF8RrgDv4NoRL7REucj2akVr7SHnsAMQEBJfIMcs
	=
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
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=OV+7WCrKAtaE3C0itYBEbvW1Pco=; b=wq4L+K3BtuyKkTOqk
	7JsZHSjSU3L+CxlSFSUx5Y1CYaTjHHkD7YHxaTFPQSbXHrdsF8B/+EmIz0HPz1Vj
	yhZ3srdurhA2Pu8+MM/N6yyXa/fSDwTTXMOoAMrj5Z3QS3JH/xDjrKEKXE45sMm0
	pofbI4nhTKxKPzzEzWTcN14WyQ=
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:	Yes, score=6.0 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD,SCAM_SUBJECT autolearn=no version=3.3.2
X-HELO:	bronze.cs.yorku.ca
Message-ID:	<530B6ED1.2060003@cse.yorku.ca>
Date:	Mon, 24 Feb 2014 11:09:53 -0500
From:	Paul Griffith <paulg AT cse DOT yorku DOT ca>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Silently configure sshd fails via system account
References:	<5307BB89 DOT 80405 AT cse DOT yorku DOT ca> <5307BDDA DOT 4040309 AT cygwin DOT com>
In-Reply-To:	<5307BDDA.4040309@cygwin.com>
X-Spam-Score:	-1.0
X-Spam-Report:	Content preview: On 02/21/2014 03:58 PM, Larry Hall (Cygwin) wrote: > On 2/21/2014 3:48 PM, Paul Griffith wrote: >> Hi, >> >> I am using a software package called WPKG (wpkg.org) to silently deploy >> Cygwin and then configure SSHD. The Cygwin installation works like a >> charm. Configuring sshd is another story. If I run my script from a admin >> command prompt, I am to setup sshd. If I run that same script from WPKG, >> it fails. The only difference is that the WPKG agent runs as the SYSTEM >> user. I assume SCCM (Microsoft System Center Configuration Manager) users >> would have the same issue since their agent also run as SYSTEM. >> >> Any ideas other than pulling apart /usr/bin/ssh-host-config and trying >> to do this manually myself ?? > > Configuring sshd can be tricky. There are plenty of failure paths so it's > best not to step off known paths to success unless you're willing to blaze > a new successful trail. With that in mind, why not run WPKG under an > account that is known to successfully install Cygwin in the normal way? > This may be close enough to a known successful path to just work. > [...] Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-IsSubscribed:	yes

On 02/21/2014 03:58 PM, Larry Hall (Cygwin) wrote:
> On 2/21/2014 3:48 PM, Paul Griffith wrote:
>> Hi,
>>
>> I am using a software package called WPKG (wpkg.org) to silently deploy
>> Cygwin and then configure SSHD. The Cygwin installation works like a
>> charm. Configuring sshd is another story. If I run my script from a admin
>> command prompt, I am to setup sshd. If I run that same script from WPKG,
>> it fails. The only difference is that the WPKG agent runs as the SYSTEM
>> user. I assume SCCM (Microsoft System Center Configuration Manager) users
>> would have the same issue since their agent also run as SYSTEM.
>>
>> Any ideas other than pulling apart /usr/bin/ssh-host-config  and trying
>> to do this manually myself ??
> 
> Configuring sshd can be tricky.  There are plenty of failure paths so it's
> best not to step off known paths to success unless you're willing to blaze
> a new successful trail.  With that in mind, why not run WPKG under an
> account that is known to successfully install Cygwin in the normal way?
> This may be close enough to a known successful path to just work.
> 

Thanks Larry,

   I have a few options to try. I post them to help others, if I achieve some measure of success.

Best Regards,
Paul


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