From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <87e383d03aac6653cc8974d1f2d3b1c1@proxima.alt.za> To: 9fans@cse.psu.edu Subject: Re: [9fans] If hostid==uid, then /lib/ndb/auth is not checked. From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Fri, 12 Mar 2004 07:56:26 +0200 Topicbox-Message-UUID: 2be820aa-eacd-11e9-9e20-41e7f4b1d025 > On Fri Mar 12 14:32:41 JST 2004, lucio@proxima.alt.za wrote: >> Well, /lib/ndb/auth indicates the speaksfor relationship. Surely uid >> X can be assumed to speakfor uid X? > > Then, every users in a domain can start their processes on > arbitary cpu servers whose host owners aren't allowed to speak > for the user? Is this the way that the speaksfor relationship > works? > Not that I can see. To be able to execute a process on a CPU server, you need to be authenticated on the file server that holds the executable. If the CPU server can't speakfor you, then you are blocked from using it. > I thought the relationship can be used to restrict which users > are allowed to run their process on cpu servers. I am still > confused with the relationship... :) I found it hard to grasp too, the mailing list archives will bear witness of that :-) But I suspect it is simpler than one expects, which is what confuses one. I have no doubt whatsoever that the speakfor relationship is quite sufficient as a security measure. ++L