From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from felloff.net ([199.191.58.38]) by ttr; Sun Aug  3 09:04:07 EDT 2014
Message-ID: <1cb65af4931640feba4b20654d86b25a@felloff.net>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: table-aware standard XMPP strategy core replication
Date: Sun, 3 Aug 2014 15:04:00 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] got file/auth/cpu server, next?
In-Reply-To: <6f9039bdb534229af91b3df9f77d109c@jitaku.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

this is wrong. auth/secstored runs its own listener and forks
into the background. you dont run it from aux/listen but start
it from the /cfg/$sysname/cpurc or /cfg/$sysname/cpustart of
your auth server.

the other error message is unrelated to secstore.

the difference between kenfs and cwfs in regard to authentication is that
cwfs uses the hosts factotum for auth instead of implementing p9sk1 itself.
the host id (user), host key (password) and authdom of your cwfs fileserver
that is read from its nvram by factotum on boot when service=cpu need to be
known by the authentication server so it can generate tickets for the machine.

it is not clear to me what you tried todo, but guessing you
want to setup an auth server?

try look here:

http://code.google.com/p/plan9front/wiki/fqa7#7.4.1_-_Configuring_an_auth_server

the key is to list the machine in ndb as the authserver for the network
which will cause it to start keyfs and the /rc/bin/service.auth listeners
on boot automatically. (you can look in /rc/bin/cpurc to see how it
does it).

--
cinap