From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] drawterm authentication failure
Date: Tue, 23 Oct 2007 09:40:12 -0400 [thread overview]
Message-ID: <a222a560e20af8bc8426b60047eee89b@quanstro.net> (raw)
In-Reply-To: <20071023132037.GA811@shodan.homeunix.net>
> I had indeed factotum running. after killing the process I could connect to
> the plan 9 server. Looks like I've implemented some authentication self hate
> on my network.
>
> Some further digging and a peek at the archives showed that upon connecting
> the following lines get appended to /mnt/factotum/log:
>
> 287: no key matches proto=9psk1 role=server dom?
> 287: failure no key matches proto=9psk1 role=server dom?
>
> Also, whenever I use drawterm without factotum (which succeeds) I get
> prompted for the secstore key twice. That seems a little odd to me.
i think there's something else going on. on the home machine i run p9p on,
i do run factotum with drawterm.
; ps auxwww|grep factotum
quanstro 4972 0.0 0.1 43648 360 ? Sl Sep13 0:00 factotum
quanstro 4975 0.0 0.0 67880 204 ? Sl Sep13 0:03 9pserve -u unix!/tmp/ns.quanstro.:0/factotum
quanstro 2202 0.0 0.2 1676 536 pts/9 S+ 09:26 0:00 grep factotum
check your profile for a path that has two calls to auth/factotum.
- erik
next prev parent reply other threads:[~2007-10-23 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 21:26 Martin Neubauer
2007-10-22 21:33 ` andrey mirtchovski
2007-10-22 22:12 ` Martin Neubauer
2007-10-22 22:22 ` erik quanstrom
2007-10-23 8:35 ` Martin Neubauer
2007-10-23 11:16 ` erik quanstrom
2007-10-23 19:34 ` Lyndon Nerenberg
2007-10-23 19:38 ` andrey mirtchovski
2007-10-23 9:28 ` sqweek
2007-10-23 13:20 ` Martin Neubauer
2007-10-23 13:40 ` erik quanstrom [this message]
2007-10-23 15:16 ` Martin Neubauer
2007-10-23 15:23 ` erik quanstrom
2007-10-23 20:06 ` Tim Wiess
2007-10-23 20:24 ` Martin Neubauer
2007-10-23 20:33 ` Tim Wiess
2007-10-24 9:55 ` johnny
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=a222a560e20af8bc8426b60047eee89b@quanstro.net \
--to=quanstro@quanstro.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).