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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Ba3GdnZXPbYJd3cI
	vsLhnDtOuSYMVupCTtxvZFq/Nh2zXX9MG2sYVb3AutO4Q4dbTJn+/4b4PpWT3/Bc
	Eg5CXIEWuZ63CQxIaNIDr8bpcSBgyzCr/dmlCJSPEQXxs4+Fd7z/NTxVtTNlV3RX
	Ss5hCr/e1FQ/qGxsxj03E1dSYdo=
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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=+kfMlRh1ww5V5NqbrcOXEd
	Mcp9I=; b=aOkGlBkHbii77YzZtXPjLkZ1B4T1lajUs/q7BiTr7uSVxETtXtYCKd
	0XUC/Kt14HFJsw5Q4y8puhIJaLJlSkM2WIVMJ65DGC5YbCypb3Sz5wFzCXr9FDTV
	YW0uypl2mJkKZXlXbqmj5AP8Src3yxfq5ur7TOYkwsOSqt4iifyZs=
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=3.0 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SCAM_SUBJECT autolearn=no version=3.3.2
X-HELO:	vms173023pub.verizon.net
Message-id:	<5307BDDA.4040309@cygwin.com>
Date:	Fri, 21 Feb 2014 15:58:02 -0500
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin 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 AT cygwin DOT com
Subject:	Re: Silently configure sshd fails via system account
References:	<5307BB89 DOT 80405 AT cse DOT yorku DOT ca>
In-reply-to:	<5307BB89.80405@cse.yorku.ca>

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.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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