From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8245d261dcde8e675c88f697bcc86cfa@plan9.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and security
Date: Sat, 19 Feb 2005 13:34:38 -0700
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
In-Reply-To: <20050219202443.DITT730.imf22aec.mail.bellsouth.net@p1.stuart.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 4efaf242-eace-11e9-9e20-41e7f4b1d025

> 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