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:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=cM
	LZM7xzCYyB1lhbe8IDC5HNmoNKxzOk+ZIv1GBh6Dw6230eJIF2XV1aWRHnLlWf+K
	r8cAef9yCMu7GwJwwEVUI3AWasKJzl0dx0vY4halhGuK5p3QeUAijvipssLWMqCT
	XtQwSR8xEYcc9HImXRPz3XDPUZdmOdidNWa4amkKY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CAG9p0OQ3Hr0wVq7eYQRHGwW79U9uAb1_13BqqY4qxuR2m8VMAQ@mail.gmail.com>
References: <5307BB89.80405@cse.yorku.ca>	<5307BDDA.4040309@cygwin.com>	<530B6ED1.2060003@cse.yorku.ca>	<CAG9p0OSzrhsqf+gZjduxU0bxzovPY31kDwH=gJ3ZUtHuj8iBZQ@mail.gmail.com>	<f5bmwgowkuh.fsf@troutbeck.inf.ed.ac.uk>	<CAG9p0OT0282=+dGWuOjk2MxMSJX0E6irg-+hD9dE1vfqDLOVyA@mail.gmail.com>	<CAG9p0OS65OC-5o-wEre+2K7+NQHQE_OzmLW9HAN8bmcYzEoG3A@mail.gmail.com>	<CAG9p0OQ3Hr0wVq7eYQRHGwW79U9uAb1_13BqqY4qxuR2m8VMAQ@mail.gmail.com>
Date: Mon, 17 Mar 2014 19:18:28 -0400
Message-ID: <CAG9p0OT9a9VZ3hx7DzQAKz1Lr2Y0niC21xr4AiYJekpMGJb2Jw@mail.gmail.com>
Subject: Re: Silently configure sshd fails via system account
From: Lord Laraby <lord.laraby@gmail.com>
To: Cygwin Mailing List <cygwin@cygwin.com>
Content-Type: text/plain; charset=UTF-8

Okay, I figured out the whole issue. The script suggested
non-privleged user sshd as the service user. I allowed that and the
user was created. However the issues the script messed up are:
1) The account was never activated - "net user sshd /active:yes" had
to be run at the command line.
2) All of the keys had permissions given to user cyg_server (which is
actually another service with different needs).
3) the /var/empty file ownership was changed to sshd (stolen from
cyg_server which also had that assigned home directory.) So, that was
correct but wrong.
4) The /var/log/sshd.log ownership was given to cyg_server (who does
not write to that log.) the cygserver.log is owned by SYSTEM!!! I do
not know why.
5) Permission modes were wrong on every file.

These were all setup by the cygwin script, all I did was answer 'yes'
to each question and provide sshd a password (twice).

This might warrant a check by the maintainer.

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