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: Tue, 23 Mar 2004 22:51:00 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Definitely no sshd on FAT32? Message-ID: <20040323215100.GY17229@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <40608855 DOT 8080605 AT ianbrandt DOT com> <40609FD8 DOT 5030103 AT ianbrandt DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40609FD8.5030103@ianbrandt.com> User-Agent: Mutt/1.4.2i On Mar 23 15:36, Ian Brandt wrote: > 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. The following checks are performed on the key file in the following order: - Not Windows NT? Yes -> Don't check permissions. - "ntea" switched on? Yes -> Check permissions. (Not applicable on FAT32) - statfs(key_file) fails? Yes -> Check permissions. - Does the file system support ACLs? (Shoud be only NTFS) Yes -> "ntsec" switched on ? Yes -> Check permissions - Don't check permissions Try to figure out what happens on your system. However, if you're running 2K or XP, I don't see a reason to keep FAT32. You can convert it to NTFS using the "convert" tool which is shipped with all NT versions. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer 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/