From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Nielsen To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil and auth Message-ID: <20030721141342.GL63873@cassie.foobarbaz.net> References: <20030720050244.GG63873@cassie.foobarbaz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i Date: Mon, 21 Jul 2003 07:13:42 -0700 Topicbox-Message-UUID: ff2fd73e-eacb-11e9-9e20-41e7f4b1d025 Here is the output. From the logs on the auth server, it looks like authentication is successful and a ticket is granted, but I must admit I am not certain. 12: start proto=p9any role=client yields phase CNeedProtos: ok 12: read 4093 in phase CNeedProtos yields phase CNeedProtos: phase: protocol phase error: read in state CNeedProtos 12: write 0 in phase CNeedProtos yields phase CNeedProtos: toosmall 2048 12: no key matches proto=p9sk1 dom=foobarbaz.net role=speakfor user? !password? 12: no key matches proto=p9sk1 dom=foobarbaz.net role=client user? !password? 12: write 20 in phase CNeedProtos yields phase CNeedProtos: needkey !password? dom=foobarbaz.net proto=p9sk1 user? 0: no key matches 0: failure no key matches 12: start proto=p9sk1 role=client dom=foobarbaz.net yields phase CHaveChal: ok 12: write 20 in phase CNeedProtos yields phase CHaveProto: ok 12: read 20 in phase CHaveProto yields phase CRelay: ok 12: read 8 in phase CHaveChal yields phase CNeedTreq: ok 12: read 8 in phase CRelay yields phase CRelay: ok 12: read 4093 in phase CNeedTreq yields phase CNeedTreq: phase: protocol phase error: read in state CNeedTreq 12: read 4093 in phase CRelay yields phase CRelay: phase: protocol phase error: read in state CNeedTreq 12: write 0 in phase CNeedTreq yields phase CNeedTreq: toosmall 141 12: write 0 in phase CRelay yields phase CRelay: toosmall 141 12: write 141 in phase CNeedTreq yields phase CHaveTicket: ok 12: write 141 in phase CRelay yields phase CRelay: ok 12: read 85 in phase CHaveTicket yields phase CNeedAuth: ok 12: read 85 in phase CRelay yields phase CRelay: ok Here is the corresponding entry from the auth server: enki Jul 21 10:05:12 tr-ok madhatter@madhatter(192.168.0.10) -> madhatter@bootes Thanks for the help. On Sun, Jul 20, 2003 at 09:28:35AM -0400, David Presotto wrote: > what authentication errors are you getting on the calling system? In > a window, 'echo -n debug > /mnt/factotum/ctl' then 'cat /dev/kprint'. > In another window, try the attach. > > Most likely, the caller doesn't know which auth server to use for > the auth domain of the file server and is just hanging up. > From: Christopher Nielsen > To: 9fans@cse.psu.edu > Date: Sat, 19 Jul 2003 22:02:44 -0700 > Subject: [9fans] fossil and auth > > I have setup a standalone fossil/venti fileserver. I also > have a standalone auth server. > > When I try to attach to main on the fileserver, I am getting > authentication failures. There are no errors in the logs on > the auth server. The output on fscons is: > > attach main as madhatter: phase error protocol phase error: read in state SNeedTicket > > Any clues as to what I might have done wrong? > > -- > Christopher Nielsen > "They who can give up essential liberty for temporary > safety, deserve neither liberty nor safety." --Benjamin Franklin -- Christopher Nielsen "They who can give up essential liberty for temporary safety, deserve neither liberty nor safety." --Benjamin Franklin