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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=wEBdoTIJ4iTcBzVVKxJa++UULVAjrXAtNKXcG1SQHTy4amUxmSuzI
	dCBkLrASRje17MjH63Iu7Wi4WCaPuD6LB7LOU9A0sC7T6ZwKK81U61GeB2jbmxs5
	Ch4TZLhVSwileQGJETaviv1scCxRlN4B/hwoypFk7xab3t5PFbVYwg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 24 Mar 2014 11:43:46 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Silently configure sshd fails via system account
Message-ID: <20140324104346.GC27624@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5307BB89.80405@cse.yorku.ca> <1395192297365-107203.post@n5.nabble.com> <5329BDA5.8060507@cse.yorku.ca> <20140319165724.GE2715@calimero.vinschen.de> <1395257718707-107220.post@n5.nabble.com> <455024617.20140320021236@yandex.ru> <CAG9p0OTaogEpCVgekztiAfD2uAPXVCJ4-_aR699LZc6+X1Z+wA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="R+My9LyyhiUvIEro"
Content-Disposition: inline
In-Reply-To: <CAG9p0OTaogEpCVgekztiAfD2uAPXVCJ4-_aR699LZc6+X1Z+wA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--R+My9LyyhiUvIEro
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 20 20:37, Lord Laraby wrote:
> Thanks for all the responses. I appreciate the attention given to
> ssh-host-config since this problem. One of my problems was that I was
> semi-braindead when I ran it and selected yes to privsep when I meant
> no. It would have been simpler, I think. Really, it it had at least
> done chmod on the files that sshd complained about, I would had had
> few problems.

It does.  Look into the code, it's just a shell script.  As for the key
files, ssh-keygen -A creates them with correct permissions, the script
just chown's them.

Apart from that, I asked for testing the new script attached to
http://cygwin.com/ml/cygwin/2014-03/msg00341.html

Without anybody testing, this will go nowhere.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--R+My9LyyhiUvIEro
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTMAxiAAoJEPU2Bp2uRE+gs04P/1OHc+7qgnA+UBtZ7HPj73ta
JMFxWIITOpK7ecJvSFwqqpvC3SQwzUKLYrttUF7k8Z2WY+vVY2r4GrU51Pn5fgXv
BUHBBtnO6/VKoturWgRrstoV84Lu/YYM1ECV62c4RMZj5slJc11s5J3QUR518D2w
znNv9J9HB5wg4bzgUozyNc7vmjlhAIacQd6aDfrgjXPP5omqefLJ2QmAdw1dRRLC
dXRZ1makaLR6TGGAXT5fc5Cd/b0hteF41HIU8yn1rgBYNnkMtAXilX9tJy8+/LZX
3vtyzMoShZgDi2ra7mkz+CMAg5hJ6Mg8jBQOxEDvSTgqnrKwHSzr/NZU+j9u2+6l
UeSsOwZqo3xS3P9Tv9onLVNbllycUe4MUFWHojZwaAHniMjLVZ9YCa1dws3bxl8q
XwxJRojAo/sH/eO2R5Af97/XoU+c2jkYdYMq3SvCfalZsyKRh+MZ74jYqX5lOsYi
e2/AJJlFA0N5iMGf9lBalKaivaHkzSzd7kqmO/MRp7TSPZVXJZqpRi/dHvkOEvul
6ij8MPwCcRM23nBc/FJlRRSBtlHZVolZHDFx1HjmkEqxZ+/1vqCbyTczSCFFDoAP
tAZJ3v1HapUk1tR1FzlJ1Tp3ow3vnVbg3Ea85fp63XK9j6/Jr1juLvDJn/y8yagt
yXC8TuxSi6I1kR4BFZ2/
=/V0u
-----END PGP SIGNATURE-----

--R+My9LyyhiUvIEro--