Date: Tue, 4 Mar 2008 10:29:49 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Definitely no sshd on FAT32?
Message-ID: <20080304092949.GN18407@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20040323215100.GY17229@cygbert.vinschen.de> <009d01c87dab$db939120$6a01a8c0@MRSLAPTOP>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009d01c87dab$db939120$6a01a8c0@MRSLAPTOP>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mar  3 22:57, Jason Pyeron wrote:
> Is there a way around the permission check on the private key files for the
> ssh client?
> 
> The key files are on a mapped drive for the domain controller. The domain
> controller was switched to samba who reports:
> [...]
> But in reality the files are 600 on the ext3 partition.

If you are a domain user then there's a good chance that your Samba
server is part of the domain and manages file permissions for domain
users as needed.  In this case try setting the environment variable
CYGWIN to contain "smbntsec":

  bash$ CYGWIN=smbntsec ssh remote-host

If that works, use this setting in your profile. Otherwise there's a
temporary solution.  Use

  bash$ CYGWIN=nontsec ssh remote-host

on every invocation of ssh.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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