From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Nigel Roles" <nigel@cotswold.demon.co.uk>
To: 9fans@cse.psu.edu
Date: Thu, 20 Jul 2000 10:22:07 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: [9fans] auth(6)
Message-ID: <3976D2CF.2800.2ED3F73D@localhost>
Topicbox-Message-UUID: e70b3520-eac8-11e9-9e20-41e7f4b1d025

I am intrigued by the /lib/ndb/auth example on auth(6) viz.

hostid=bootes
	uid=!sys uid=!adm uid=*

Bootes is typically a fileserver, but I feel this doesn't make sense
in this case. Authentication is about convincing a fileserver that
a client may speak for a userid, so should I think of bootes 
as a terminal/cpu server in this context?

The long and short is

1.	if I want to auth/login on my terminal (T) as user (U) do I need
   
	hostid=T
		uid=U

	in my /lib/ndb/auth?

2.	if I want to cpu(1) from my terminal to my cpu server (C), do I
	need

	hostid=C
		uid=!sys uid=!adm uid=*

	even if it is also the authentication server?