From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <bf908c8c562167f0acedb663f4141b23@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Tue,  1 May 2007 09:13:58 -0400
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyfs warnings
In-Reply-To: <20070501125658.GK2624@hermes.my.domain>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 5471af64-ead2-11e9-9d60-3106f5b1d025

> 
> - overwriting my nvram with bla

i think what you have should work, but i think you'd rather zero
out the whole file:

	dd -if /dev/zero -of /n/9fat/plan9.nvr -count 1

> - truncating the /adm/keys file with echo '' > /adm/keys
> - rebooting, filling in password and secstore phrase
> - killing keyfs
> - starting auth/keyfs on the server console

i don't understand this step.  if keyfs is running on the console
of your auth server, restarting it shouldn't make any difference.

(you should always be dealing with keyfs and changeuser from the
console of the auth server.)

> - creating new keys with auth/changeuser for bootes and another user
> - rebooting
> 
> After that I am able to log in as bootes but not the other user (the
> user is present on the fossil filesystem)

where are you "logging in" from.  i assume, since you mentioned this
is a combined fs/cpu/auth server, that you are drawterming in from
another machine?

> 
> When I now kill/restart keyfs on the server keyfs prints the
> following warnings:
> % auth/keyfs
> keyfs: warning: bad status in key file
> keyfs: warning: bad status in key file
> keyfs: warning: bad status in key file
> 4 keys read
> 
> 1. Shouldn't there be only 2 keys as I have added 2 users?
> 2. When trying to auth/debug the user login still fails
> 3. lc /mnt/keys displays garbage

what is in /mnt/keys on the console after you have just booted the machine?

- erik