This is the mail archive of the
mailing list for the Cygwin project.
Re: Definitely no sshd on FAT32?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 4 Mar 2008 10:29:49 +0100
- Subject: Re: Definitely no sshd on FAT32?
- References: <20040323215100.GY17229@cygbert.vinschen.de> <009d01c87dab$db939120$6a01a8c0@MRSLAPTOP>
- Reply-to: cygwin at cygwin dot 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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html