From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some thoughts about auth*
Date: Wed, 6 Nov 2002 21:42:11 -0500 [thread overview]
Message-ID: <b9179cfcffc60e631b49f5352f287d91@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
There used to be a key for connecting to other resources and
one for letting people log onto the console so that they could
use it (for cpu and file servers). The latter was the authkey
and we eventually gave up on the function altogether. The naming
is hokey, I'm to blame.
[-- Attachment #2: Type: message/rfc822, Size: 2112 bytes --]
From: "Roman V. Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
To: 9fans@cse.psu.edu
Subject: [9fans] some thoughts about auth*
Date: Thu, 7 Nov 2002 03:25:33 +0300
Message-ID: <20021107032533.A30255@unicorn.math.spbu.ru>
1. Isn't it strange that getauthkey.c:getauthkey actually
returns .machkey ? Is there any historical reason for
it to be getauthkey() especially when there is a
field in Nvrsafe called .authkey ?
2. I'm not exactly sure that I understand why Nvrsafe has
this .authkey member in it. The only place where it is
being used by the regular Plan9, not a dedicated Plan9
FS is in cmd/disk/kfs/auth.c which doesn't seem to make
much sense, when nobody sets it up.
As a matter of fact, I was able to spot it, only because
in my particular case auth/wrkey *always* sets it to
'roman' which is honorable, but very weird :)
All in all, I'd be grateful for any insights or explanations.
Thanks in advance,
Roman.
next reply other threads:[~2002-11-07 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 2:42 presotto [this message]
[not found] <fce4571861a826ddf4677ec3cecbe995@plan9.bell-labs.com>
2002-11-12 17:37 ` Roman V. Shaposhnick
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 19:47 Richard Miller
2002-11-08 2:56 ` Roman V. Shaposhnick
2002-11-07 0:25 Roman V. Shaposhnick
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=b9179cfcffc60e631b49f5352f287d91@plan9.bell-labs.com \
--to=presotto@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).