Message-ID: <44C048FC.9040000@cygwin.com>
Date: Thu, 20 Jul 2006 23:24:44 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060112 Fedora/1.5-1.fc4.remi Thunderbird/1.5 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin services using uid 400, not SYSTEM. Why?
References: <4460B3A7 DOT 8020201 AT cygwin DOT com> <447F175B DOT 8020505 AT hotmail DOT com> <44BE35F4 DOT 7080900 AT hotmail DOT com DOT INVALID> <44BE3756 DOT 4060509 AT hotmail DOT com DOT INVALID> <44BE501D DOT 30209 AT hotmail DOT com DOT INVALID> <44C03C01 DOT 8070700 AT hotmail DOT com DOT INVALID>
In-Reply-To: <44C03C01.8070700@hotmail.com.INVALID>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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

Shaddy Baddah wrote:
> Hi again,
> 
> On 7/20/2006 1:30 AM, Shaddy Baddah wrote:
>> I'm so sorry I didn't pick up on this earlier. Thanks for your 
>> attention. If you have any ideas on the UID 400 problem, I'd still be 
>> very interested to hear what was happening on that.
> 
> One last bit of diagnosis. In my earlier email, I claimed that the 
> displaying of UID 400 instead of SYSTEM was solved after running 
> cygserver-config.
> 
> Well, I got a little muddled. I finally got back to the original system 
> that I experienced the problem on (now perhaps not really so much a 
> problem as I thought. I'll elaborate).
> 
> The attachment is a log of commands that I executed that highlights the 
> problem very clearly. You will see that after running *exim-config* (not 
> cygserver-config), the Cygwin services correctly display as uid SYSTEM, 
> and not 400.
> 
> Looking at the exim-config script, I am totally bewildered how this 
> could have had any effect on the problem. It looks quite tame (in terms 
> of editing rights, etc...). Perhaps someone might have better insight 
> into this.
> 
> I am now also not so sure that the processes showing UID 400 was really 
> a problem in the first place. In my earlier email, inetd was not working 
> because of an unrelated problem. I am actually trying to reproduce the 
> problem now, and just ascertain if there was a *rights* problem 
> associated, as it did very much appear to me to be earlier.


Only the SYSTEM user on <W2K3 systems has the permissions to switch user
contexts out-of-the-box.  On W2K3, SYSTEM doesn't have it either, which is
why the openssh package creates a sshd_server user on those platforms if
you run ssh-host-config and answer the questions truthfully. ;-)  400 is
not the UID for SYSTEM (at least not by default).  If you had inetd
running under user ID 400 and hadn't made changes yourself to ensure
that this UID mapped to the SYSTEM user's SID, none of the services running
under inetd would have permissions to switch users.  So while maybe this
wasn't the only component of your problem, it's certainly one big one.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (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/