9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and security
Date: Sat, 19 Feb 2005 13:34:38 -0700	[thread overview]
Message-ID: <8245d261dcde8e675c88f697bcc86cfa@plan9.ucalgary.ca> (raw)
In-Reply-To: <20050219202443.DITT730.imf22aec.mail.bellsouth.net@p1.stuart.org>

> In message <ee9e417a05021911205354182a@mail.gmail.com>, Russ Cox writes:
>>You can echo -n refresh >/net/dns too, but you weren't
>>changing DNS-related stuff.
>
> Cool.  What about changes to authdom?  Who uses authdom
> and how?  In response to Andrey's questions (which I seem
> to have sent just to him instead of the list), my local
> file has the normal auth=sources... line and it also
> has an authdom=home in the section for my local network.
> I'm not quite sure what it means for both of them to be
> there.  In fact, when I first set the system up, I commented
> out the auth=sources line.  But today, I figured that was
> at the heart of my problem getting replica/pull to work.
>
> Brian L. Stuart

i don't seem to have received your message. i blame the university's email servers.

for authdom= the only requirement that's really important is to make
sure you've synchronized it with what cpu server user (bootes in most
cases) thinks it's running in.  i.e.  when you boot it make sure your
authdom= in nvram is the same as the authdom= entry in ndb for the
network you're booting in:

ipnet=ucalgary ip=136.159.220.0 ipmask=255.255.255.0
	proto=tcp
	[...]
	authdom=plan9.ucalgary.ca

when i invalidate the nvram (or change the password) i supply
plan9.ucalgary.ca as the authdom on the next boot of the cpu server.

andrey



  reply	other threads:[~2005-02-19 20:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2005-02-19 19:20   ` [9fans] Venti security in view of SHA-1 exploit Paul Lalonde
2005-02-19 19:26     ` andrey mirtchovski
2005-02-19 19:35       ` Paul Lalonde
2005-02-19 20:14         ` Tim Newsham
2005-02-20  4:24           ` Karl Magdsick
2005-02-19 20:15     ` Russ Cox
2005-02-19 22:25       ` boyd, rounin
2005-02-19 22:44         ` [9fans] Venti security in view of SHA-1 exploity William Josephson
2005-02-19 22:48           ` boyd, rounin
2005-02-20 18:08             ` William Josephson
2005-02-19 23:21         ` [9fans] Venti security in view of SHA-1 exploit Bruce Ellis
2005-02-20  1:00           ` Tim Newsham
2005-02-20  3:53           ` Karl Magdsick
2005-02-19 19:52 ` [9fans] Drawterm and security Skip Tavakkolian
2005-02-19 19:11   ` blstuart
2005-02-21 11:30   ` Robert Raschke
2005-02-21 19:20     ` geoff
     [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

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=8245d261dcde8e675c88f697bcc86cfa@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).