From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 23 Oct 2007 15:20:37 +0200
From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] drawterm authentication failure
Message-ID: <20071023132037.GA811@shodan.homeunix.net>
References: <20071022212644.GA888@shodan.homeunix.net>
	<140e7ec30710230228q840c0c9i104b06f8c083e738@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <140e7ec30710230228q840c0c9i104b06f8c083e738@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Topicbox-Message-UUID: d67ca07c-ead2-11e9-9d60-3106f5b1d025

* sqweek (sqweek@gmail.com) wrote:
>  I only ever muddled about with auth when I was getting my plan9 box
> up so I may be misremembering, but isn't gettickets related to
> factotum?
>  Is there a factotum running on the host you're drawterming from or
> are you just relying on what drawterm provides in that respect? Might
> be worth a try.
> -sqweek

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.

	Martin