From: "Nigel Roles" <nigel@cotswold.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] auth(6)
Date: Thu, 20 Jul 2000 10:22:07 +0100 [thread overview]
Message-ID: <3976D2CF.2800.2ED3F73D@localhost> (raw)
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?
next reply other threads:[~2000-07-20 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 9:22 Nigel Roles [this message]
2000-07-20 12:10 Russ Cox
2000-07-20 12:10 presotto
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=3976D2CF.2800.2ED3F73D@localhost \
--to=nigel@cotswold.demon.co.uk \
--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).