9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: plan9fans@ntlworld.nospam.com
To: 9fans@cse.psu.edu
Subject: [9fans] auth on terminal
Date: Thu, 25 Mar 2004 15:45:03 +0000	[thread overview]
Message-ID: <fc96dff62b30c0acb11a094a1192e484@snellwilcox.com> (raw)

Thanks for the help guys but I'am still not there.

>...then your factotums are nonpersistent.
My factotum's state is sort-of persistant as I run 
	auth/aescbc -d < /n/cdrom/secrets | read -m > /mnt/factotum/ctl
in my profile to populate it.

> ...keyfs and authsrv in the same namespace,
During my attempts to run auth/keyfs it was in the same namespace
as aux/listen, they where started on the command line in a Rio window.

>...nvram setup + factotum -S should solve your problems.
If I run factotum -S and populate it then I guess it would stop
the password prompts from behind rio (I have not tried, see below).

> ..-- auth/debug is your friend
If I don't run the authserver then auth/debug says I have a problem,
however if I do run the auth server it is happy, on bowth systems. 

However I now think I don't need an auth server as all I want
is a direct connection between two machines, both running as me.

I tried turning on factotums debug but the issue wasn't "obvious"
Again I did:

	cpu -h paris
	!Adding key: proto=p9sk1 dom=quintile.net
	user[steve]: 
	!Adding key: proto=p9sk1 dom=quintile.net
	user[steve]: 
	...

Factotum debug from larch

287: start proto=p9any role=client yields phase CNeedProtos: ok
287: read 4093 in phase CNeedProtos yields phase CNeedProtos: phase: protocol phase error: read in state CNeedProtos
287: write 0 in phase CNeedProtos yields phase CNeedProtos: toosmall 2048
287: start proto=p9sk1 role=client dom=mydom.net yields phase CHaveChal: ok
287: write 78 in phase CNeedProtos yields phase CHaveProto: ok
287: read 19 in phase CHaveProto yields phase CRelay: ok
287: read 8 in phase CHaveChal yields phase CNeedTreq: ok
287: read 8 in phase CRelay yields phase CRelay: ok
287: read 4093 in phase CNeedTreq yields phase CNeedTreq: phase: protocol phase error: read in state CNeedTreq
287: read 4093 in phase CRelay yields phase CRelay: phase: protocol phase error: read in state CNeedTreq
287: write 0 in phase CNeedTreq yields phase CNeedTreq: toosmall 141
287: write 0 in phase CRelay yields phase CRelay: toosmall 141
287: write 141 in phase CNeedTreq yields phase CNeedTreq: needkey proto=p9sk1 dom=mydom.net user? !password?
287: write 141 in phase CRelay yields phase CRelay: needkey proto=p9sk1 dom=mydom.net user? !password?


Factotum debug from paris

8: start proto=p9any role=server yields phase SHaveProtos: ok
8: no key matches proto=p9sk1 role=server dom? 
8: read 78 in phase SHaveProtos yields phase SNeedProto: ok
8: read 4093 in phase SNeedProto yields phase SNeedProto: phase: protocol phase error: read in state SNeedProto
8: write 0 in phase SNeedProto yields phase SNeedProto: toosmall 1
8: write 1 in phase SNeedProto yields phase SNeedProto: toosmall 2
8: write 2 in phase SNeedProto yields phase SNeedProto: toosmall 3
8: write 3 in phase SNeedProto yields phase SNeedProto: toosmall 4
8: write 4 in phase SNeedProto yields phase SNeedProto: toosmall 5
8: write 5 in phase SNeedProto yields phase SNeedProto: toosmall 6
8: write 6 in phase SNeedProto yields phase SNeedProto: toosmall 7
8: write 7 in phase SNeedProto yields phase SNeedProto: toosmall 8
8: write 8 in phase SNeedProto yields phase SNeedProto: toosmall 9
8: write 9 in phase SNeedProto yields phase SNeedProto: toosmall 10
8: write 10 in phase SNeedProto yields phase SNeedProto: toosmall 11
8: write 11 in phase SNeedProto yields phase SNeedProto: toosmall 12
8: write 12 in phase SNeedProto yields phase SNeedProto: toosmall 13
8: write 13 in phase SNeedProto yields phase SNeedProto: toosmall 14
8: write 14 in phase SNeedProto yields phase SNeedProto: toosmall 15
8: write 15 in phase SNeedProto yields phase SNeedProto: toosmall 16
8: write 16 in phase SNeedProto yields phase SNeedProto: toosmall 17
8: write 17 in phase SNeedProto yields phase SNeedProto: toosmall 18
8: write 18 in phase SNeedProto yields phase SNeedProto: toosmall 19
8: write 19 in phase SNeedProto yields phase SRelay: ok
8: read 4093 in phase SNeedChal yields phase SNeedChal: phase: protocol phase error: read in state SNeedChal
8: read 4093 in phase SRelay yields phase SRelay: phase: protocol phase error: read in state SNeedChal
8: write 0 in phase SNeedChal yields phase SNeedChal: toosmall 8
8: write 0 in phase SRelay yields phase SRelay: toosmall 8
8: write 8 in phase SNeedChal yields phase SHaveTreq: ok
8: write 8 in phase SRelay yields phase SRelay: ok
8: read 141 in phase SHaveTreq yields phase SNeedTicket: ok
8: read 141 in phase SRelay yields phase SRelay: ok
8: read 4093 in phase SNeedTicket yields phase SNeedTicket: phase: protocol phase error: read in state SNeedTicket
8: read 4093 in phase SRelay yields phase SRelay: phase: protocol phase error: read in state SNeedTicket
8: write 0 in phase SNeedTicket yields phase SNeedTicket: toosmall 85
8: write 0 in phase SRelay yields phase SRelay: toosmall 85

-Steve


             reply	other threads:[~2004-03-25 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 15:45 plan9fans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-25 16:16 Tiit Lankots
2004-03-25 15:14 Tiit Lankots
2004-03-25 15:09 Tiit Lankots
2004-03-25 15:00 Tiit Lankots
2004-03-25 15:09 ` andrey mirtchovski
2004-03-25 15:10 ` andrey mirtchovski
2004-03-25 13:36 plan9fans
2004-03-25 13:43 ` Fco.J.Ballesteros
2004-03-25 13:55   ` David Presotto
2004-03-25 14:51     ` Steve Simon
2004-03-25 15:31       ` Richard Miller
2004-03-25 14:00 ` Richard Miller

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=fc96dff62b30c0acb11a094a1192e484@snellwilcox.com \
    --to=plan9fans@ntlworld.nospam.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).