Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <40609FD8.5030103@ianbrandt.com>
Date: Tue, 23 Mar 2004 15:36:40 -0500
From: Ian Brandt <ian AT ianbrandt DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Definitely no sshd on FAT32?
References: <40608855 DOT 8080605 AT ianbrandt DOT com> <Pine DOT GSO DOT 4 DOT 56 DOT 0403231441420 DOT 19995 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.56.0403231441420.19995@slinky.cs.nyu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Igor Pechtchanski wrote:
> 
> It is, but it won't be as secure.  See below.
 >
> FYI, "ntsec" is only ignored for the *disk* volumes, but it is used for a
> bunch of other NT-enabled features that have nothing to do with disks
> (e.g., user context switching).  However, "ntsec" is on by default now, so
> you aren't losing this functionality by omitting it.

Good to know.

> Try turning off "StrictModes" in your sshd_config.

Looks like it's already set to no in the installed config.  From man 
sshd_config it looks like StrictModes applies to checks of the home 
directory and files for the user logging in.  I had tried installing the 
service with '-t' option to sshd, but apparently it still does the perm 
checks on the host keys even in test mode.

Regards,

Ian

--
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/