Message-Id: <200608161821.k7GIL5VW024015@tigris.pounder.sol.net>
To: cygwin AT cygwin DOT com
From: cygzz AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
Subject: group"S-1-2-0"(users who login locally)in ssh;windows 2003
Date: Wed, 16 Aug 2006 13:21:02 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

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.

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

--
thanks,
Tom Rodman

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