X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:	Re: ssh: issue with file permissions on Samba network shares
Date:	Tue, 01 Apr 2008 08:11:12 -0700
Lines:	28
Message-ID:	<fstjak$8t3$1@ger.gmane.org>
References:	<47F23916 DOT 5020608 AT lists DOT cichon DOT com> <47F23DB1 DOT 9080207 AT sbcglobal DOT net>
Mime-Version:	1.0
User-Agent:	Thunderbird 2.0.0.12 (Windows/20080213)
In-Reply-To:	<47F23DB1.9080207@sbcglobal.net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Greg Chicares wrote:
> On 2008-04-01 13:31Z, Public Mailing Lists wrote:
>>> Permissions 0644 for '/home/xxxxxxx/.ssh/id_rsa' are too open.
> Try this:
> chmod 600 ~/.ssh/id_rsa
If that doesn't work (after the chmod try an ls -l to verify the mod) 
then it could be that your home directory is being shared by Samba and 
Samba is not configured properly (i.e. being part of the domain) such 
that it carries all of the users credentials. If that be the case then 
you'll never get the chmod to actually work. IIRC (it's been a few 
clients ago) if the Samba server is pretty bare then it's only using an 
smbpasswd file. Such a file does not have enough structure to carry all 
the information about Windows users credentials. Samba recommends 
configuring stuff to be part of the domain and to use a TDB (which it 
calls a Trivial Database) or an LDAP style configuration so that the 
Samba server is servicing all of the SMB protocol properly (Forgive any 
of my terminology errors). IOW if your home directory share were on a 
Windows server I bet everything would be working but since it's probably 
on a Linux system and being shared with Samba it might be that you don't 
have it fully configured.

At that previous client I could not get the admin to update the Samba 
configuration. My workaround (hazy) was to do the ssh but somehow to 
specify that my ~/.ssh was local, temporarily - i.e. for the ssh only. 
IIRC it wasn't ideal but it sorta worked.
-- 
Andrew DeFaria <http://defaria.com>
The beatings will continue until morale improves.


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

- Raw text -