From mboxrd@z Thu Jan  1 00:00:00 1970
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Date: Mon, 10 Aug 2009 02:40:17 -0700
User-Agent: KMail/1.11.4 (Linux/2.6.27-gentoo-r8; KDE/4.2.4; i686; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200908100240.18429.corey@bitworthy.net>
Subject: [9fans] machine key, secstore key, hostowner password
Topicbox-Message-UUID: 3f591f92-ead5-11e9-9d60-3106f5b1d025


When creating a cpu/auth kernel, one needs to create a variety of
key/passwords - the machine key, the secstore key, and the hostowner password.

I _think_ I have the basics understood regarding the purpose of these, but one
thing I'm uncertain of:

Aside from the point in which they're each first set, when will they ever be
manually used again?

When I say "when will they be manually used again", I mean... will a user ever
be prompted to enter them again in order to perform some administrative action
or another?

I've yet to actually be prompted for any one of them again after the initial
setup of my cpu/auth server. I imagine at some point I will need to configure
or setup something which will require one of passwords in order to proceed?


Also, what sorts of issues arise if one were to specify non-matching hostowner
passwords, i.e. - when you first boot up after invaliding nvram, you are asked
to specify a hostowner password, then again you are asked to supply a
hostowner password when you run 'auth/changeuser <hostowner>'...

The documentation states that these are supposed to match. But what sorts
of symptoms will result if you, for instance, typo'd the auth/changeuser
<hostowner> password?


Thanks!