From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20070511115855.A3FDC1E8C3A@holo.morphisms.net>
References: <20070511115855.A3FDC1E8C3A@holo.morphisms.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4F0C5D9E-2609-46BC-BCE4-79E049EFF6F9@tinker.com>
Content-Transfer-Encoding: 7bit
From: Kim Shrier <kim@tinker.com>
Subject: Re: [9fans] Hopefully, one last problem
Date: Sat, 12 May 2007 17:28:05 -0600
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 67070944-ead2-11e9-9d60-3106f5b1d025

I have fixed the problem with logging in from a drawterm to my
cpu/auth/file server.  Based on a suggestion by Russ Cox, I
changed the bootes password.  I first set the bootes password
and secstore key to the same value.  I was still unable to log
in as kim and when I tried to log in as bootes, it complained
that I had typed in an incorrect password.  After staring at
the notes I had taken during the initial installation, I saw
that the first time a ran auth/keyfs, I got the following
output:

     term% auth/keyfs
     bad nvram key
     bad authentication id
     bad authentication domain
     can't read /dev/key, please enter machine key
     Password: some_long_password
     Confirm password: some_long_password
     term%

This password was different than the one I was originally
using for bootes's secstore key and password.  I have now
set the secstore key and the password to some_long_password.

After rebooting the cpu/auth/file server, I can log in both
as bootes and as kim from a drawterm.  I am going to leave
things alone with regard to configuration until I get a
little more familiar with Plan 9.

I really appreciate all the help I received from this list.

Kim