Re: [9fans] 4th ed. cpu/auth server setup problems.

Re: [9fans] 4th ed. cpu/auth server setup problems.

[Russ Cox]

No server found means your ndb isn't quite right.
In particular, you need an authdom= tuple in the
entry that lists the auth server.

ipnet=lanl-acl172-net
	ip=172.16.82.0
	ipmask=255.255.255.0
	auth=172.16.82.9
>>	authdom=acl.lanl.gov
	dnsdomain=acl.lanl.gov

Russ

Re: [9fans] 4th ed. cpu/auth server setup problems.

[Dean Prichard]

thanks Russ, that was it. everything is working fine now.

-dp

On Tue, 30 Apr 2002, Russ Cox wrote:

> Date: Tue, 30 Apr 2002 21:41:23 -0400
> From: Russ Cox <rsc@plan9.bell-labs.com>
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] 4th ed. cpu/auth server setup problems.
>
> No server found means your ndb isn't quite right.
> In particular, you need an authdom= tuple in the
> entry that lists the auth server.
>
> ipnet=lanl-acl172-net
> 	ip=172.16.82.0
> 	ipmask=255.255.255.0
> 	auth=172.16.82.9
> >>	authdom=acl.lanl.gov
> 	dnsdomain=acl.lanl.gov
>
> Russ
>

[9fans] 4th ed. cpu/auth server setup problems.

[dpx]

Before trying to upgrade our cpu/auth server I thought I would give a try at
setting up a standalone 4th ed. cpu/auth server and try to test it out with
a 4th ed. terminal. I have done the usual setup, built kernel, modified cpurc
setup, /lib/ndb/local, /lib/ndb/auth, added users etc, but I can't seem to
authenticate to it, using cpu, ssh, or telnet, below are some examples. Does
anyone have any ideas on what i might be doing wrong?

thx,

-dp


term% cpu -h bela

!Adding key: dom=acl.lanl.gov proto=p9sk1
user[dpx]:
password:
!
cpu: can't authenticate: bela: auth_proxy rpc write: \x01bootes: no auth server found for acl.lanl.gov
term% ssh bela

!Adding key: proto=pass server=bela service=ssh user=dpx
password:
!
ssh: client authentication failed

--------------------------------------
an attempt to turn on some debugging:

term% auth/factotum -d -a bela.acl.lanl.gov
term% ssh bela
1: no key matches proto=pass service=ssh server=bela user=dpx user? !password?
1: start proto=pass service=ssh server=bela user=dpx yields phase 0: needkey !password? proto=pass server=bela service=ssh user? user=dpx

!Adding key: proto=pass server=bela service=ssh user=dpx
password:
!
2: start proto=pass service=ssh server=bela user=dpx yields phase 0: ok
2: read 17 in phase 0 yields phase 0: ok
ssh: client authentication failed
term% cpu -h bela
3: start proto=p9any role=client yields phase CNeedProtos: ok
3: read 4093 in phase CNeedProtos yields phase CNeedProtos: phase: protocol phase error: read in state CNeedProtos
3: write 0 in phase CNeedProtos yields phase CNeedProtos: toosmall 2048
3: no key matches  proto=p9sk1 dom=acl.lanl.gov role=speakfor user? !password?
3: no key matches  proto=p9sk1 dom=acl.lanl.gov role=client user? !password?
3: write 19 in phase CNeedProtos yields phase CNeedProtos: needkey !password? dom=acl.lanl.gov proto=p9sk1 user?

!Adding key: dom=acl.lanl.gov proto=p9sk1
user[dpx]:
password:
!
3: start proto=p9sk1 role=client dom=acl.lanl.gov yields phase CHaveChal: ok
3: write 19 in phase CNeedProtos yields phase CHaveProto: ok
3: read 19 in phase CHaveProto yields phase CRelay: ok
3: read 8 in phase CHaveChal yields phase CNeedTreq: ok
3: read 8 in phase CRelay yields phase CRelay: ok
3: read 4093 in phase CNeedTreq yields phase CNeedTreq: phase: protocol phase error: read in state CNeedTreq
3: read 4093 in phase CRelay yields phase CRelay: phase: protocol phase error: read in state CNeedTreq
3: write 0 in phase CNeedTreq yields phase CNeedTreq: toosmall 141
3: write 0 in phase CRelay yields phase CRelay: toosmall 141
3: failure no auth server found for acl.lanl.gov
3: write 141 in phase CNeedTreq yields phase CNeedTreq: failure no auth server found for acl.lanl.gov
3: write 141 in phase CRelay yields phase CRelay: failure no auth server found for acl.lanl.gov
cpu: can't authenticate: bela: auth_proxy rpc write: \x01bootes: no auth server found for acl.lanl.gov
term%

--------------------------------

on bela(cpu/auth server):

/sys/log/listen:

bela Apr 30 13:36:45 tcp call for tcp22 on chan /net/tcp/21 (172.16.82.12)
bela Apr 30 13:38:00 tcp call for tcp22 on chan /net/tcp/21 (172.16.82.12)
bela Apr 30 13:38:33 il call for il17010 on chan /net/il/2 (172.16.82.12)
bela Apr 30 13:39:38 tcp call for tcp22 on chan /net/tcp/21 (172.16.82.12)
bela Apr 30 13:40:08 il call for il17010 on chan /net/il/2 (172.16.82.12)
bela Apr 30 13:40:24 tcp call for tcp22 on chan /net/tcp/21 (172.16.82.12)

/sys/log/ssh:

bela Apr 30 13:35:42 [82] connect from 172.16.82.12!18692
/bin/aux/sshserve: got unexpected <early eof: short net read: auth server protocol botch> message
bela Apr 30 13:36:45 [85] connect from 172.16.82.12!18693
/bin/aux/sshserve: got unexpected <early eof: short net read: auth server protocol botch> message
bela Apr 30 13:38:00 [88] connect from 172.16.82.12!18694
/bin/aux/sshserve: got unexpected <early eof: short net read: auth server protocol botch> message
bela Apr 30 13:39:38 [92] connect from 172.16.82.12!18695
/bin/aux/sshserve: got unexpected <early eof: short net read: auth server protocol botch> message
bela Apr 30 13:40:24 [96] connect from 172.16.82.12!18696
/bin/aux/sshserve: got unexpected <early eof: short net read: auth server protocol botch> message

--------------------
/lib/ndb/local:

#
#  files comprising the database, use as many as you like, see ndb(6)
#
database=
	file=/lib/ndb/local
	file=/lib/ndb/common

ipnet=lanl172-net
	ip=172.16.0.0
	ipmask=255.255.0.0
	ipsubmask=255.255.255.0


ipnet=lanl-acl172-net
	ip=172.16.82.0
	ipmask=255.255.255.0
	auth=172.16.82.9
	dnsdomain=acl.lanl.gov

#auth server
ip=172.16.82.9 sys=bela ether=0060cf20833f dom=bela.acl.lanl.gov proto=il
# terminal
ip=172.16.82.12 sys=jerq ether=00d059aaea2e dom=jerq.acl.lanl.gov proto=il