Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/