9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: [9fans] machine key, secstore key, hostowner password
Date: Mon, 10 Aug 2009 02:40:17 -0700	[thread overview]
Message-ID: <200908100240.18429.corey@bitworthy.net> (raw)


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!




             reply	other threads:[~2009-08-10  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10  9:40 Corey [this message]
2009-08-10  9:46 ` Corey
2009-08-10  9:55   ` Steve Simon
2009-08-10 10:17     ` Corey
2009-08-10 10:30       ` Steve Simon

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=200908100240.18429.corey@bitworthy.net \
    --to=corey@bitworthy.net \
    --cc=9fans@9fans.net \
    /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).