From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6ff137bc8218a00cb469b5040c10c62b@snellwilcox.com> From: "Steve Simon" To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-koupwcumfhpyphfwrozfoyxdxq" Subject: [9fans] (no subject) Date: Mon, 19 Apr 2004 09:29:04 +0100 Topicbox-Message-UUID: 5e20d1d4-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-koupwcumfhpyphfwrozfoyxdxq Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, To reiterate, I am just trying to boot a terminal (paris) from a cpu/auth/file server (felix). I get an authentication failure on startup, though everything up to secstore works fine. To debug this I put a copy of the distribution on the terminal and booted that standalone. I used auth/debug to check authenticatioon is set up properly; it is happy (see auth-debug.out). I then tried to use cpu(1) to attach to the file server (see cpu.out) and its fails. I have enabled factotum debug at both ends and included the logs of these also. plan9.ini, local, and cpurc are the files from the server felix, factotum is an extract from my secstore factotum file. I don't understand how cpu can fail when auth/debug succeeds. what have I missed? -Steve --upas-koupwcumfhpyphfwrozfoyxdxq Content-Type: multipart/mixed; boundary="upas-juvmbgpqelwxlhfdsttmyjtrfm" Content-Disposition: inline This is a multi-part message in MIME format. --upas-juvmbgpqelwxlhfdsttmyjtrfm Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Disposition: attachment; filename=auth-debug.out Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --upas-juvmbgpqelwxlhfdsttmyjtrfm Content-Type: application/octet-stream Content-Disposition: attachment; filename="auth-debug.out.suspect" p9sk1 key: proto=p9sk1 dom=home.mydom.net user=steve !password? successfully dialed auth server password for steve@home.mydom.net [hit enter to skip test]: ticket request using steve@home.mydom.net key succeeded cpu server owner for domain home.mydom.net [bootes]: password for bootes@home.mydom.net [hit enter to skip test]: ticket request using bootes@home.mydom.net key succeeded --upas-juvmbgpqelwxlhfdsttmyjtrfm-- --upas-koupwcumfhpyphfwrozfoyxdxq Content-Type: multipart/mixed; boundary="upas-gvxwfqfjxqqquktctjjrxuefsp" Content-Disposition: inline This is a multi-part message in MIME format. --upas-gvxwfqfjxqqquktctjjrxuefsp Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Disposition: attachment; filename=cpu.out Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --upas-gvxwfqfjxqqquktctjjrxuefsp Content-Type: application/octet-stream Content-Disposition: attachment; filename="cpu.out.suspect" cpu: can't authenticate: felix: auth_proxy rpc write: cpu: srvauth:: auth server protocol botch --upas-gvxwfqfjxqqquktctjjrxuefsp-- --upas-koupwcumfhpyphfwrozfoyxdxq Content-Disposition: attachment; filename=cpurc Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit #!/bin/rc echo -n cpu > /env/service date > /env/boottime # replace FILESERVER with the name of your file server # here we start with kfs, your local disk file system fileserver=felix # replace FACEDOM with the local domain to be used in the faces database facedom=FACEDOM ip/ipconfig -N ether /net/ether0 add ip/ipconfig loopback /dev/null 127.1 # mount points mntgen -s slashn && chmod 666 /srv/slashn # name translation, cs sets /dev/sysname ndb/cs sysname=`{cat /dev/sysname} ndb/dns -r # parallelism for mk NPROC=`{wc -l /dev/sysstat} NPROC=`{echo $NPROC|sed 's/ .*//'} prompt=($sysname^'# ' ' ') # pick a timeserver closer to you when you can or we'll get clogged aux/timesync -n # uncomment the following for booting other systems ip/dhcpd ip/tftpd # If you are on an auth server, start these before listening: # auth/keyfs -wp -m /mnt/keys /adm/keys auth/cron >>/sys/log/cron auth/secstored # services available to networks aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service il for(i in m) /bin/bind -a '#'^$i /dev bind -b $home/bin/rc /bin --upas-koupwcumfhpyphfwrozfoyxdxq Content-Disposition: attachment; filename=factotum Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit key proto=p9sk1 dom=home.mydom.net user=steve !password=xxxxxxx --upas-koupwcumfhpyphfwrozfoyxdxq Content-Disposition: attachment; filename=local Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit # # network database # # to force this file to be re-read type # !echo -n refresh >/net/cs ip=127.0.0.1 sys=localhost dom=localhost database= file=/lib/ndb/local file=/lib/ndb/common # laptop sys=paris ether=0020af8d6140 ip=192.168.0.3 authdom=home.mydom.net dom=paris.mydom.net bootf=/386/9pc.gz # home server sys=felix ether=00609765ed59 ip=192.168.0.5 authdom=home.mydom.net dom=felix.mydom.net # home, inside firewall ipnet=home ip=192.168.0.0 ipmask=255.255.255.0 ipgw=192.168.0.1 # dns=194.168.4.100 dns=194.168.8.100 # dnsdomain=mydom.net pop3=webmail.snellwilcox.com smtp=smtp-uk.snellwilcox.com authdom=home.mydom.net nntp=news.ntlworld.com ntp=gb.public.ntp.get-time.net fs=192.168.0.5 cpu=192.168.0.5 auth=192.168.0.5 auth=felix authdom=home.mydom.net --upas-koupwcumfhpyphfwrozfoyxdxq Content-Type: multipart/mixed; boundary="upas-wspesfsceloythsjmzmybcrbmz" Content-Disposition: inline This is a multi-part message in MIME format. --upas-wspesfsceloythsjmzmybcrbmz Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Disposition: attachment; filename=plan9.ini Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --upas-wspesfsceloythsjmzmybcrbmz Content-Type: application/octet-stream Content-Disposition: attachment; filename="plan9.ini.suspect" [menu] menuitem=terminal menuitem=server menudefault=server,5 [terminal] bootfile=sd00!9fat!9pcf venti=#S/sd06/arenas0 [server] venti=#S/sd06/arenas0 bootfile=sd00!9fat!9pccpuf nobootprompt=local!#S/sd00/fossil [common] *nomp=1 vgasize=640x480x8 monitor=multisync110 mouseport=ps2 distname=plan9 ether0=type=elnk3 media=10BaseT scsi0=type=ncr53c8xx bootargs=local!#S/sd00/fossil bootdisk=local!#S/sd00/fossil --upas-wspesfsceloythsjmzmybcrbmz-- --upas-koupwcumfhpyphfwrozfoyxdxq Content-Type: multipart/mixed; boundary="upas-foyunvtqpstwzmdyxywtpwjnxk" Content-Disposition: inline This is a multi-part message in MIME format. --upas-foyunvtqpstwzmdyxywtpwjnxk Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Disposition: attachment; filename=felix.fact.debug Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --upas-foyunvtqpstwzmdyxywtpwjnxk Content-Type: application/octet-stream Content-Disposition: attachment; filename="felix.fact.debug.suspect" 1: start proto=p9any role=server yields phase SHaveProtos: ok 1: no key matches proto=p9sk1 role=server dom? 1: failure no key matches proto=p9sk1 role=server dom? 1: read 24 in phase SHaveProtos yields phase SNeedProto: ok 1: read 4093 in phase SNeedProto yields phase SNeedProto: phase: protocol phase error: read in state SNeedProto 1: write 0 in phase SNeedProto yields phase SNeedProto: toosmall 1 1: write 1 in phase SNeedProto yields phase SNeedProto: toosmall 2 1: write 2 in phase SNeedProto yields phase SNeedProto: toosmall 3 1: write 3 in phase SNeedProto yields phase SNeedProto: toosmall 4 1: write 4 in phase SNeedProto yields phase SNeedProto: toosmall 5 1: write 5 in phase SNeedProto yields phase SNeedProto: toosmall 6 1: write 6 in phase SNeedProto yields phase SNeedProto: toosmall 7 1: write 7 in phase SNeedProto yields phase SNeedProto: toosmall 8 1: write 8 in phase SNeedProto yields phase SNeedProto: toosmall 9 1: write 9 in phase SNeedProto yields phase SNeedProto: toosmall 10 1: write 10 in phase SNeedProto yields phase SNeedProto: toosmall 11 1: write 11 in phase SNeedProto yields phase SNeedProto: toosmall 12 1: write 12 in phase SNeedProto yields phase SNeedProto: toosmall 13 1: write 13 in phase SNeedProto yields phase SNeedProto: toosmall 14 1: write 14 in phase SNeedProto yields phase SNeedProto: toosmall 15 1: write 15 in phase SNeedProto yields phase SNeedProto: toosmall 16 1: write 16 in phase SNeedProto yields phase SNeedProto: toosmall 17 1: write 17 in phase SNeedProto yields phase SNeedProto: toosmall 18 1: write 18 in phase SNeedProto yields phase SNeedProto: toosmall 19 1: write 19 in phase SNeedProto yields phase SNeedProto: toosmall 20 1: write 20 in phase SNeedProto yields phase SNeedProto: toosmall 21 1: write 21 in phase SNeedProto yields phase SNeedProto: toosmall 22 1: write 22 in phase SNeedProto yields phase SNeedProto: toosmall 23 1: write 23 in phase SNeedProto yields phase SNeedProto: toosmall 24 1: write 24 in phase SNeedProto yields phase SRelay: ok 1: read 4093 in phase SNeedChal yields phase SNeedChal: phase: protocol phase error: read in state SNeedChal 1: read 4093 in phase SRelay yields phase SRelay: phase: protocol phase error: read in state SNeedChal 1: write 0 in phase SNeedChal yields phase SNeedChal: toosmall 8 1: write 0 in phase SRelay yields phase SRelay: toosmall 8 1: write 8 in phase SNeedChal yields phase SHaveTreq: ok 1: write 8 in phase SRelay yields phase SRelay: ok 1: read 141 in phase SHaveTreq yields phase SNeedTicket: ok 1: read 141 in phase SRelay yields phase SRelay: ok 1: read 4093 in phase SNeedTicket yields phase SNeedTicket: phase: protocol phase error: read in state SNeedTicket 1: read 4093 in phase SRelay yields phase SRelay: phase: protocol phase error: read in state SNeedTicket 1: write 0 in phase SNeedTicket yields phase SNeedTicket: toosmall 85 1: write 0 in phase SRelay yields phase SRelay: toosmall 85 1: failure auth server protocol botch 1: write 85 in phase SNeedTicket yields phase SNeedTicket: failure auth server protocol botch 1: write 85 in phase SRelay yields phase SRelay: failure auth server protocol botch 9fat: --upas-foyunvtqpstwzmdyxywtpwjnxk-- --upas-koupwcumfhpyphfwrozfoyxdxq Content-Type: multipart/mixed; boundary="upas-hmhswltorqmkltrqlkmfhkbfcy" Content-Disposition: inline This is a multi-part message in MIME format. --upas-hmhswltorqmkltrqlkmfhkbfcy Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Disposition: attachment; filename=paris.fact.debug Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --upas-hmhswltorqmkltrqlkmfhkbfcy Content-Type: application/octet-stream Content-Disposition: attachment; filename="paris.fact.debug.suspect" paris% cat /dev/kprint 1: start proto=p9any role=client yields phase CNeedProtos: ok 1: read 4093 in phase CNeedProtos yields phase CNeedProtos: phase: protocol phase error: read in state CNeedProtos 1: write 0 in phase CNeedProtos yields phase CNeedProtos: toosmall 2048 1: start proto=p9sk1 role=client dom=home.mydom.net yields phase CHaveChal: ok 1: write 24 in phase CNeedProtos yields phase CHaveProto: ok 1: read 24 in phase CHaveProto yields phase CRelay: ok 1: read 8 in phase CHaveChal yields phase CNeedTreq: ok 1: read 8 in phase CRelay yields phase CRelay: ok 1: read 4093 in phase CNeedTreq yields phase CNeedTreq: phase: protocol phase error: read in state CNeedTreq 1: read 4093 in phase CRelay yields phase CRelay: phase: protocol phase error: read in state CNeedTreq 1: write 0 in phase CNeedTreq yields phase CNeedTreq: toosmall 141 1: write 0 in phase CRelay yields phase CRelay: toosmall 141 1: write 141 in phase CNeedTreq yields phase CHaveTicket: ok 1: write 141 in phase CRelay yields phase CRelay: ok 1: read 85 in phase CHaveTicket yields phase CNeedAuth: ok 1: read 85 in phase CRelay yields phase CRelay: ok 1: read 4093 in phase CNeedAuth yields phase CNeedAuth: phase: protocol phase error: read in state CNeedAuth 1: read 4093 in phase CRelay yields phase CRelay: phase: protocol phase error: read in state CNeedAuth 1: write 0 in phase CNeedAuth yields phase CNeedAuth: toosmall 13 1: write 0 in phase CRelay yields phase CRelay: toosmall 13 1: failure auth server protocol botch 1: write 13 in phase CNeedAuth yields phase CNeedAuth: failure auth server protocol botch 1: write 13 in phase CRelay yields phase CRelay: failure auth server protocol botch --upas-hmhswltorqmkltrqlkmfhkbfcy-- --upas-koupwcumfhpyphfwrozfoyxdxq--