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 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ANNOUNCEMENT] Re: Updated: OpenSSH-3.4p1-1 Date: Thu, 27 Jun 2002 13:51:41 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark A." To: "Chris Metcalf" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g5RHqhA30672 > -----Original Message----- > From: Chris Metcalf [mailto:metcalf AT incert DOT com] > Sent: Thursday, June 27, 2002 1:28 PM > To: cygwin AT cygwin DOT com > Subject: Re: [ANNOUNCEMENT] Re: Updated: OpenSSH-3.4p1-1 > > > On Thu, 27 Jun 2002, Corinna Vinschen wrote: > > The Cygwin version modifies that test so that if /var/empty resides > > on a FAT or FAT32 filesystem, or if ntsec is not activated, the > > ownership isn't tested at all. If /var/empty is on a NTFS > filesystem > > and ntsec is switched on, the ownership is checked against the user > > running sshd. > > Thanks. This was indeed the problem (I'm running ntfs, ntsec). > > I saw your note about one small change and it didn't occur to > that it was > exactly the one thing that I went into the "official" sources > in search of! > > Some words to this effect should go into > /usr/doc/openssh/README.privsep > as well, since it still talks about a "chown root:sys > /var/empty" being > required. > Perhaps this information should go into /usr/doc/Cygwin/openssh-3.4p1-1.README instead? My understanding of the documentation setup is that Cygwin-specific information goes into /usr/doc/Cygwin, while the "official" (non-Cygwin-specific) documents go into /usr/doc/. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/