9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] problems setting up auth service
Date: Wed,  6 Jun 2001 09:08:02 -0400	[thread overview]
Message-ID: <20010606130806.2293519A12@mail.cse.psu.edu> (raw)

I've just gotten one person past their auth server problems
with the following set of instructions.  He never saw the
	password: password: ...
problem, but he did see pretty much everything else.

The instructions in start.ps are a little out of date.
I'll work on that too when I get a free minute or two.

This sets up a system as a cpu/auth server.  If you want
to run auth service from a terminal, ask me and I'll
build a different set of instructions.  
------------------------------------------

0) make sure all the wraps are installed

1) build a cpu kernel that contains a kfs (local file server)

% cd /sys/src/9/pc
% mk 'CONF=pccpudisk'

2) copy it to where you boot from, you could change /n/9fat/plan9.ini
   to use a different file name to bot from but this may be easier

% 9fat:
% cp 9pccpudisk /n/9fat/9pcdisk

3) make sure there's an empty key file, keyfs screws up when it creates
  one.  create it as the user you are going to run the cpu server as.
  Call that user bootes.  You can call it whatever you want but you'ld
  better make sure you do a 'disk/kfscmd newuser newname' before you do.

% disk/kfscmd allow
% rm /adm/keys
% disk/kfscmd 'create /adm/keys bootes bootes 660'

4) make sure you have /bin/cpurc starting the following:

auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null >[2=1]
auth/cron >>/sys/log/cron >[2=1] &

if(! test -e /rc/bin/service.auth/il566){
	mv /rc/bin/service.auth/authsrv.il566 /rc/bin/service.auth/il566
	mv /rc/bin/service.auth/authsrv.tcp567 /rc/bin/service.auth/tcp567
	mv /rc/bin/service/il566 /rc/bin/service/_il566
	mv /rc/bin/service/tcp567 /rc/bin/service/_tcp567
}

# services available to networks
aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service il
aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp

4) reboot, this time you'll come up as a cpuserver. it will ask for
   an authid, authdom, and password.  Use bootes, whatever.com, and
   whatever password you want.

5) The system will start keyfs and the right listeners.  On the console
   you can now start creating accounts.

  Start with the user that the auth server runs as.  BE SURE TO USE
  THE SAME PASSWORD YOU JUST LOGGED THE AUTH SERVER IN AS!!!!!

% auth/changeuser bootes
...

% auth/changeuser guest
....

6) Now change /lib/ndb/local on other systems to let them know where the
   auth server is.  Look at /sys/doc/start.ps for how.


                 reply	other threads:[~2001-06-06 13:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010606130806.2293519A12@mail.cse.psu.edu \
    --to=presotto@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).