From: "Frank Palazzolo" <palazzol@comcast.net>
To: 9fans@cse.psu.edu
Subject: [9fans] drawterm/telnet authentication
Date: Wed, 23 Jun 2004 21:26:19 -0400 [thread overview]
Message-ID: <40D9F57B.29957.1F3C54BE@localhost> (raw)
Hi,
I have a cpu/auth server and I'm trying to get drawterm working. I
have the dreaded "cannot authenticate with p9" problem when I use the
correct password for my bootes user. Also, telnet with the correct
response gives the protocol botch message.
auth/debug seems fine. I ran factotum in debug mode and got the
following transaction during a drawterm connection:
2: start proto=p9sk2 role=server yields phase SHaveTreq: ok
2: read 141 in phase SHaveTreq yields phase SNeedTicket: ok
2: read 4093 in phase SNeedTicket yields phase SNeedTicket: toosmall
85
2: failure auth server protocol botch
2: write 85 in phase SNeedTicket yields phase SNeedTicket: failure
auth server protocol botch
also...
cat /mnt/factotum/ctl
key proto=p9sk1 user=bootes dom=mynetwork !hex? !password?
Thanks for any help - I checked back through the archives before
posting, and tried a few other things, to no avail. I'm sure it's
something simple...
Thanks,
-Frank
reply other threads:[~2004-06-24 1:26 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=40D9F57B.29957.1F3C54BE@localhost \
--to=palazzol@comcast.net \
--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).