9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] got file/auth/cpu server, next?
Date: Sun, 3 Aug 2014 15:04:00 +0200	[thread overview]
Message-ID: <1cb65af4931640feba4b20654d86b25a@felloff.net> (raw)
In-Reply-To: <6f9039bdb534229af91b3df9f77d109c@jitaku.localdomain>

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


  reply	other threads:[~2014-08-03 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03  9:55 kokamoto
2014-08-03 13:04 ` cinap_lenrek [this message]
2014-08-04  0:01   ` [9front] " kokamoto
2014-08-04  0:14   ` kokamoto
2014-08-03 15:14 kokamoto

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=1cb65af4931640feba4b20654d86b25a@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /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).