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: Wed, 18 Aug 2004 23:59:44 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: upgrading openssh 3.8.1p1-1 -> 3.9p1-1 breaks privilege separation Message-ID: <20040818215944.GT10590@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <87n00siknk DOT fsf AT beth DOT swift DOT xxx> <20040818152348 DOT GI10590 AT cygbert DOT vinschen DOT de> <4123ACA8 DOT 1010801 AT acm DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4123ACA8.1010801@acm.org> User-Agent: Mutt/1.4.2i On Aug 18 12:23, David Rothenberger wrote: > On 8/18/2004 8:23 AM, Corinna Vinschen wrote: > >As a temporary measure, please add the -r option when starting sshd. > >I haven't found the exact culprit so far, but the above flag will help. > > > >Thanks for the report. It's embarassing that I didn't find the error > >myself since I had accidentally switched off privilege separation a few > >days ago :-( > > I did not experience this problem when I upgraded and I thought that I > had privilege separation enabled. Is there any easy way to tell if it > is on or not? You mean, other than looking into /etc/sshd_config? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project 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/