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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Tue, 5 Aug 2003 11:22:58 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Ville Herva <vherva AT niksula DOT hut DOT fi>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Administrator lacking super-user privileges on cygwin installation
In-Reply-To:	<20030805150743.GB221723@niksula.cs.hut.fi>
Message-ID:	<Pine.GSO.4.44.0308051110450.6333-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Tue, 5 Aug 2003, Ville Herva wrote:

> On Tue, Aug 05, 2003 at 08:07:43AM -0400, you [Igor Pechtchanski] wrote:
> >
> > IIRC, the default installation of sshd as service used the event log for
> > all output, rather than /var/log/sshd.log (though I'm not too sure on this
> > one)...
>
> It certainly seems to, in the event log, there are sshd generated entries.
>
> > However, error code 255 means that the executable could not be executed.
>
> Ack.
>
> > Check the permissions on sshd ("ls -l /usr/sbin/sshd")
>
>  $ ls -l /usr/sbin/sshd
>  -rwxrwxrwx    1 Administ mkgroup_   286720 May 22 23:44 /usr/sbin/sshd
                            ^^^^^^^^

See <http://cygwin.com/cygwin-ug-net/ntsec.html#NTSEC-RELEASE1.3.20> (a
bit out of date, it seems, but should still give you the general idea).

> That should be runnable by SYSTEM, right?

Well, how about getting a SYSTEM-owned shell and checking? ;-)

> > and the mounts ("/", at least, should be a system mount).
>
>  $ mount
>  c:\cygwin\bin on /usr/bin type system (binmode)
>  c:\cygwin\lib on /usr/lib type system (binmode)
>  c:\cygwin on / type system (binmode)
>
>  $ echo $CYGWIN
>  binmode ntsec tty

Make sure the SYSTEM user doesn't have any *user* mounts (by running
"mount" from a SYSTEM-owned shell).
	Igor
P.S. For instructions on getting a SYSTEM-owned shell, search Google for
"at /interactive" on "cygwin.com".
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


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