Message-Id: <200608162049.k7GKnTTE024729@tigris.pounder.sol.net>
From: cygzz AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: group"S-1-2-0"(users who login locally)in ssh;windows 2003
In-reply-to: <ebvsj3$bu7$1@sea.gmane.org>
References: <200608161821 DOT k7GIL5VW024015 AT tigris DOT pounder DOT sol DOT net> <ebvsj3$bu7$1 AT sea DOT gmane DOT org>
Date: Wed, 16 Aug 2006 15:49:29 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Thanks for your help Matthew.

On Wed 8/16/06 14:44 CDT mwoehlke wrote:
> Tom Rodman wrote:
> > Hosts effected:
> > 
> >   several boxes running windows 2003 server w/cygwin (1.5.20s(0.155/4/2) 20060403 13:33:45)
> > 
> > Problem (or feature?): 
> > 
> >   when you ssh to these boxes, and run:
> > 
> >     $WINDIR/system32/whoami /all |grep -q S-1-2-0 || echo OOPs # "OOPS" echos :-<
> > 
> >     "S-1-2-0" == "Users who log on to terminals locally (physically) connected to the system."
> > 
> > Under windows 2000 (also a different cygwin version), ssh sessions show group membership
> > in "S-1-2-0":
> > 
> >    $ '/drv/c/Program Files/Resource Kit/whoami' /all|grep S-1-2-0
> >    [Group  9] = "LOCAL"  S-1-2-0
> > 
> > The reason I care is that is that several tools we call from cygwin, will
> > not run unless the session is in S-1-2-0.
> 
> What makes you say this? 

I can't prove that membership in S-1-2-0 is required for these tools - it's a guess.

> What tools?

The're fairly obscure - Telelogic CM CLI tools to report on Informix databases.

> > I'm not sure if this is a cygwin version issue, or due to windows 2003.
> > Any thoughts/can others test this in an ssh session?:
> > 
> >   $WINDIR/system32/whoami /all |grep -q S-1-2-0 || echo OOPs
> 
> FWIW, on my 2k3 box, I show up as a member in S-1-2-0 both logged in 
> "locally" (via Remote Desktop Sharing, with which I have never had 
> anything "not work") and via Cygwin sshd. 

That's encouraging. The tool that fails for us (only in ssh) has been
doing so on several previous versions of cygwin, in all cases under
windows 2003; my hunch is there is something specific about our setup
that is causing the ssh session to not be in S-1-2-0. Days (or weeks from
now) I will try upgrading cygwin, and followup with cygcheck output if
the problem persists.

--snip

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