From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4277DCC4.5010806@asgaard.homelinux.org>
Date: Tue,  3 May 2005 22:19:16 +0200
From: =?ISO-8859-1?Q?=22Nils_O=2E_Sel=E5sdal=22?= <noselasd@asgaard.homelinux.org>
User-Agent: Mozilla Thunderbird 1.0.2-1 (X11/20050323)
MIME-Version: 1.0
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] Auth woes.
References: <4277BB46.6020001@asgaard.homelinux.org>	
	<ee9e417a05050311007a7101fd@mail.gmail.com>	
	<4277C5DB.7050601@asgaard.homelinux.org>
	<ee9e417a05050311465174d433@mail.gmail.com>
In-Reply-To: <ee9e417a05050311465174d433@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 44c18ffa-ead0-11e9-9d60-3106f5b1d025

Russ Cox wrote:
> after the cron job has run, what does cat /mnt/factotum/ctl show?
>=20
As I told Russ, the key gets disabled. I added a flog call to
factotum/p9sk1.c;

convM2T(tbuf, &s->t, (char*)s->key->priv);
if(s->t.num !=3D AuthTc){
	disablekey(s->key);
	flog("disabling key. s->t.num=3D%d",s->t.num);
	if(askforkeys){

(Ok I later realized t.num is a char)
Which seems to be what is disabling the key.
/mnt/factotum/log says disabling key. s->t.num=3D41,
(on next reboot it said s->t.num=3D76)

The whole log is;

2: no key matches proto=3Dp9sk1 role=3Dserver dom?
2: failure no key matches proto=3Dp9sk1 role=3Dserver dom?
3: no key matches proto=3Dp9sk1 dom=3Dfiane.intra role=3Dclient dom=3Dfia=
ne.intra user?=20
!password? owner=3Dupas owner=3D*
3: failure no key matches proto=3Dp9sk1 dom=3Dfiane.intra role=3Dclient=20
dom=3Dfiane.intra user? !password?
disabling key. s->t.num=3D76
3: failure bad key
4: no key matches proto=3Dp9sk1 role=3Dserver user? dom?
4: failure no key matches proto=3Dp9sk1 role=3Dserver user? dom?

--
Nils O. Sel=E5sdal