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 Date: Mon, 11 Oct 2004 19:19:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: SSHD installation defaults / security Message-ID: <20041011171930.GR6702@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <001801c4af85$87bb3280$3300a8c0 AT heroldy> <20041011114328 DOT GN6702 AT cygbert DOT vinschen DOT de> <20041011165347 DOT GC13985 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041011165347.GC13985@trixie.casa.cgf.cx> User-Agent: Mutt/1.4.2i On Oct 11 12:53, Christopher Faylor wrote: > On Mon, Oct 11, 2004 at 12:49:09PM -0400, Igor Pechtchanski wrote: > >On Mon, 11 Oct 2004, Corinna Vinschen wrote: > >>I'm not sure if the package should require cygrunsrv, though. The > >>/usr/share/doc/Cygwin/openssh.README file mentions that cygrunsrv is > >>required to install sshd as service on NT systems. > > > >Well, in the spirit of CGF's comment about tetex-x11 requiring X > >because of xdvi (see > >), perhaps > >openssh *should* require cygrunsrv. > > Or, (Corinna will probably kill me for saying this but...) maybe it's > time to split openssh into opensh-server and openssh-client? OpenSSH's Makefile doesn't contain this split between client and server applications and files. I'd rather not add our own installation rules. > openssh-server could rely on cygrunsrv. I've added cygrunsrv to the dependencies. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/