Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<423226F1.50809@real.com>
Date:	Fri, 11 Mar 2005 15:17:05 -0800
From:	Jeff Silverman <jsilverman AT real DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems starting SSHD
References:	<4231D448 DOT 7090208 AT real DOT com> <Pine DOT GSO DOT 4 DOT 61 DOT 0503111235510 DOT 23792 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To:	<Pine.GSO.4.61.0503111235510.23792@slinky.cs.nyu.edu>

Dr. Pechtchanski:

We solved our little problem with sshd failing to start, thanks to your 
clues.

First, /var/empty must be owned by SYSTEM. Second, /etc/ssh_host_key 
must be owned by SYSTEM or else protected 644. Protecting it 644 is a 
bad idea because it compromises security.

On the Windows/2K machine, which worked the first try, *all* of the 
files /etc/ssh* are owned by SYSTEM:None and /var/empty and 
/var/log/sshd.log are owned by SYSTEM:root



Thank you for your assistance.


Jeff




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -