From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ur; Tue Feb 23 09:31:25 EST 2016
Message-ID: <00309c019f5a1bd4279bbff5c5ddf007@felloff.net>
Date: Tue, 23 Feb 2016 15:31:17 +0100
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] drawterm qid re-use
In-Reply-To: <1c4ade6aefca933daf5c1d8225eb0afb@titan.jitaku.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: factory database map/reduce solution 

> Hmm, you have your version of drawterm...

there was no other way. all the work done for dp9ik
authentication is of no use if i cannot diable the
p9sk1 tickets in the authentication server. as long
as the authentication server issues des encrypted
tickets that can simply be bruteforced, we cannot
have security.

drawterm was the last blocker. now that it can speak
dp9ik, we can start disabling the p9sk1 i the as
by default.

also being able to finally fix some long outstanding
issues like qid collisions and windows drive letters
and x11 graphics glitches is a bonus.

--
cinap