From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Russ Cox <russcox@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Drawterm and security
Date: Sat, 19 Feb 2005 17:37:48 -0600 [thread overview]
Message-ID: <20050219233809.JSIC2073.imf18aec.mail.bellsouth.net@p1.stuart.org> (raw)
In-Reply-To: Your message of Sat, 19 Feb 2005 17:42:54 -0500 . <ee9e417a05021914422bf17403@mail.gmail.com>
In message <ee9e417a05021914422bf17403@mail.gmail.com>, Russ Cox writes:
>> I almost literally heard the bell ring this time. So
>> when I try to initiate an authentication, it's up to the
>> server to tell me what authentication domain he wants to
>> use. Then I look up to find a auth= autodom= entry so
>> that I know who to talk to in order to do authenticate
>> in that domain. So if I have an authdom=home entry in my
>> local network section, then anyone who wants to connect
>> to my server will be told to authenticate using the
>> home domain. It's then up to the client to know what
>> auth server to use.
>
>All this is true except that the choice of authdom=home
>does not come from your local network section. The choice
>of authdom comes from factotum, and it offers the client
>a list of possible domains. In particular, it offers any domain
>on a p9sk1 key that isn't marked with role=client.
That makes sense. So the putting auth= and authdom= into
the local network section is to tell your clients the
appropriate domain->server mapping for your network,
right? It also raises the question, where does factotum
get that first key so that he has a dom to send out-
from nvram?
Thanks,
Brian L. Stuart
next prev parent reply other threads:[~2005-02-19 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSI.4.61.0502191055110.3971@malasada.lava.net>
2005-02-19 21:09 ` Brian L. Stuart
2005-02-19 22:42 ` Russ Cox
2005-02-19 23:37 ` Brian L. Stuart [this message]
2005-02-19 18:37 Brian L. Stuart
2005-02-19 18:48 ` andrey mirtchovski
2005-02-19 21:00 ` Brian L. Stuart
2005-02-19 18:58 ` Russ Cox
2005-02-19 19:15 ` blstuart
2005-02-19 19:20 ` Russ Cox
2005-02-19 20:24 ` blstuart
2005-02-19 20:34 ` andrey mirtchovski
2005-02-19 19:52 ` Skip Tavakkolian
2005-02-19 19:11 ` blstuart
2005-02-21 11:30 ` Robert Raschke
2005-02-21 19:20 ` geoff
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=20050219233809.JSIC2073.imf18aec.mail.bellsouth.net@p1.stuart.org \
--to=blstuart@bellsouth.net \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).