From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3F4D75B2.9030801@plan9.bell-labs.com>
From: Russ Cox <rsc@plan9.bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NAT'ing a drawterm connection
References: <Pine.LNX.4.44.0308242324350.3501-100000@fbsd.cpsc.ucalgary.ca> <002e01c36b05$68bc5f50$c901a8c0@cc77109e> <3F4A0CBB.9020306@plan9.bell-labs.com> <007301c36b31$b68bf160$c901a8c0@cc77109e>
In-Reply-To: <007301c36b31$b68bf160$c901a8c0@cc77109e>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Aug 2003 23:23:30 -0400
Topicbox-Message-UUID: 244b5a3e-eacc-11e9-9e20-41e7f4b1d025

Bruce Ellis wrote:

>NO.  There is no devssl in drawterm.  Not hard but not done.
>And and a firewall doesn't stop the sniff.  Type away.
>
>
>>No, the connection is SSL encrypted using the key established by the auth.
>>
>>Russ
>>

Umm, oops.  I could have sworn this happened when I updated drawterm
for the new draw model, years ago.  I'm really amazed.  If someone wants to
make the change, importing devssl should be trivial.

As for the drawterm changes, if someone wants to be the official maintainer
of drawterm, that'd be great.  Send me mail and we can arrange write
permission
on sources.

If others want to do the 9P2000 changes, it's really quite straightforward.
I haven't bothered because I have grander changes in mind, so the protocol
change by itself doesn't seem worth it to me.

Russ