From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <3258eb01a201159c8e06f2b23d8b8f4b@proxima.alt.za>
References: <3258eb01a201159c8e06f2b23d8b8f4b@proxima.alt.za>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <d27a7e748cad46f195041c57a651ad70@ar.aichi-u.ac.jp>
Content-Transfer-Encoding: 7bit
From: arisawa@ar.aichi-u.ac.jp
Subject: Re: [9fans] factotum & invalid entries
Date: Mon,  7 Feb 2005 18:15:41 +0900
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 0445e3e0-ead0-11e9-9d60-3106f5b1d025

> 	key proto=p9sk1 dom=proxima.alt.za user=lucio !password?
> 	key proto=p9sk1 dom=outside.plan9.bell-labs.com user=lucio !password?
>
> and I'd religiously delkey the second entry before retrying for
> exactly the reasons raised by pac and Russ.
>
> Now, I submit that factotum would be right to "delkey" the second
> entry as soon as it is aware that the authentication failed.  It
> would, by default, overwrite the entry if I changed the password, but
> it is not allowed to do so (by design) if I change the username.

If factotum automatically changed
	key proto=p9sk1 dom=proxima.alt.za user=lucio !password?
	disabled key proto=p9sk1 dom=outside.plan9.bell-labs.com user=lucio
!password?
when it know the list is useless, you can add
	key proto=p9sk1 dom=outside.plan9.bell-labs.com user= proxima
!password?
at the place of disabled entry. this is what you desire.
What is the problem?
If factotum have deleted erroneous record then factotum put next record
only at the end.  If order is matter this make a problem.

Kenji Arisawa