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 Message-ID: <421E06F6.4010306@unipex.it> Date: Thu, 24 Feb 2005 17:55:18 +0100 From: Michele Petrazzo User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: sshd and authorized_keys References: <421DEAF3 DOT 8070807 AT unipex DOT it> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Igor Pechtchanski wrote: >>debug1: trying public key file /ssh/keys/authorized_keys >>Authentication refused: bad ownership or modes for directory / >> >>I don't want to modify ownership of / ! >> >>Is there a method to tell to sshd to don't make control of >>ownership? >>Or, is there a method for make my idea work? > > > Sure. Move the "ssh" directory one level down, and set the permissions on > the containing directory appropriately. E.g., > > mkdir /private && chmod 755 /private && mv /ssh /private > Why make this? What change if I put ssh into private? > However, I don't see why you're so resistant with making "/" non-writeable > for anyone that's not your user... Since you're the only user on the > machine, the only other concievable users that would be affected are > internal Windows users, like "LocalSystem" (a.k.a. SYSTEM), and I can see > no reason in allowing them to write to "/" (you can always make > subdirectories of root writeable). I did't think this! With only a simple chown Administrator.Administrators / all work ok! > Igor Thanks, Michele -- 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/