delorie.com/archives/browse.cgi | search |
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: | <42323797.10906BE1@dessent.net> |
Date: | Fri, 11 Mar 2005 16:28:07 -0800 |
From: | Brian Dessent <brian AT dessent DOT net> |
Organization: | My own little world... |
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> <423226F1 DOT 50809 AT real DOT com> |
X-IsSubscribed: | yes |
Reply-To: | cygwin AT cygwin DOT com |
Jeff Silverman wrote: > 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. Are you using /usr/bin/ssh-host-config to install the daemon? It should take care of all of that for you automatically. Brian -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |