From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth(6)
Date: Thu, 20 Jul 2000 08:10:48 -0400 [thread overview]
Message-ID: <200007201210.IAA04483@cse.psu.edu> (raw)
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?
When you log into your terminal at boot time
as U, T=U. If you want to be someone else (V)
while logged in as U, you need
hostid=U
uid=V
hostid might be more understandable as "hostuid".
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=*
Yes.
even if it is also the authentication server?
Yes. The auth server is a process that interprets
the rules (among other things). It doesn't distinguish
itself (at least, not in this regard) from other
CPU servers.
Russ
next reply other threads:[~2000-07-20 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 12:10 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-20 12:10 presotto
2000-07-20 9:22 Nigel Roles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200007201210.IAA04483@cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).