Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <02e101c357e0$82350730$6902a8c0@markonius>
From: "Mark Priest" <mark DOT priest AT cox DOT net>
To: <cygwin AT cygwin DOT com>, "Myk Melez" <myk AT aol DOT net>
Cc: <cygwin AT cygwin DOT com>
References: <3F299C67 DOT 1070700 AT aol DOT net> <3F29C4F1 DOT 8010805 AT cygwin DOT com>
Subject: Re: Administrator lacking super-user privileges on cygwin installation
Date: Thu, 31 Jul 2003 23:53:45 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Myk,

I assume you are using Openssh?  If you installed Openssh as a Windows
service then SYSTEM is the owner of the files, otherwise the owner is
whatever user did the installation.  This is, of course, assuming that you
used the ssh-host-config script in /bin.  However, I have installed it both
ways and I have not received the error you are describing.  You might want
to check the value of the CYGWIN environment variable.  By default ntsec is
turned on but if that variable includes "nontsec" or "ntea" then that might
be what is causing your problem.

-Mark

----- Original Message -----
From: "Larry Hall" <cygwin-lh AT cygwin DOT com>
To: "Myk Melez" <myk AT aol DOT net>
Cc: <cygwin AT cygwin DOT com>
Sent: Thursday, July 31, 2003 9:40 PM
Subject: Re: Administrator lacking super-user privileges on cygwin
installation


> Myk Melez wrote:
>
> > I have two machines with what look like identical cygwin installations
> > on them, but the Administrator account on one of them doesn't have
> > super-user privileges.  This causes sshd not to have access to
> > /home/some-user/.ssh (which is restricted to only "some-user") and thus
> > prevents key-based authentication.  Regular password-based
> > authentication works, so the problem isn't sshd itself.  Logging in as
> > the Administrator and doing "ls /home/some-user/.ssh/*" gives me a
> > "permission denied" error, which also confirms that the problem is with
> > the permissions of the Administrator account and not sshd.
> >
> > The Administrator NT accounts (and Administrators NT groups) seem
> > identical on the two machines, as are permissions for the C:\cygwin
> > directory.  Both systems had old cygwin installations on them that we
> > blew away before installing the latest.  What am I missing?
>
>
> 1. SYSTEM is the account that sshd runs as, not administrator.  It's
>     the only default account that has permissions to switch user contexts
>     without authenticating the new user through Windows password mechanism
>     (for NT/W2K/XP).
>
> 2. Only the owner of the private key files in .ssh should have permissions
>     to access these files.  Public key files should be readable by anyone.
>     You'll want to check the permissions on these files relative to the
>     above.
>
> 3. Generally, you should read <http://cygwin.com/problems.html>.
>
>
>
> --
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 838 Washington Street                   (508) 893-9889 - FAX
> Holliston, MA 01746
>
>
> --
> 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/
>



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