From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] machine key, secstore key, hostowner password
Date: Mon, 10 Aug 2009 03:17:26 -0700 [thread overview]
Message-ID: <200908100317.26957.corey@bitworthy.net> (raw)
In-Reply-To: <2423e34dee842afe8e50088e1150889e@quintile.net>
On Monday 10 August 2009 02:55:58 Steve Simon wrote:
> The machine key _is_ the hostowners password, DES encrypted with
> the hostowner's name, the details are in the code.
>
The hostowners password stored in nvram, and the hostowner's password
stored in the authentication database served by keyfs can be set to different
strings - but the documentation suggests that they should match:
http://plan9.bell-labs.com/wiki/plan9/Configuring_a_Standalone_CPU_Server
"
REBOOT
Reboot the machine. [...]
It will ask for an authid, authdom, secstore key, and password. [...] Remember
the password, you will need it again later when creating the 'bootes' user.
"
... and later:
"
AUTHENTICATION SERVER CONFIGURATION
Firstly, you must set the password for bootes using auth(8) and the password
you just entered during bootup:
auth/changeuser bootes
"
I'm curious if their are repercussions, and of what nature, if they do not
match.
> the secstore key is just that, it us useful for storing account
> details that the hostowner may need - for example I keep my
> sources account in hostowner's secstore so I can cpu -u bootes
> to become hostowner and then do a pull.
>
> I have to type in the hostowner's secstore key about once a year - though
> it is read from the nvram un onlock the hostowners secstore on every boot
> of my cpu/auth/file server.
>
> I use the hostowner's key once a week or so to cpu in to do a pull or if
> I need access to the server's /dev/kmesg or devices.
>
Cool thanks -- so, it's the machine key that is only ever used by the machine
itself and never by a human being after it has been set?
next prev parent reply other threads:[~2009-08-10 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 9:40 Corey
2009-08-10 9:46 ` Corey
2009-08-10 9:55 ` Steve Simon
2009-08-10 10:17 ` Corey [this message]
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=200908100317.26957.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).