From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 32420 invoked from network); 22 Oct 2021 10:14:22 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 22 Oct 2021 10:14:22 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by 4ess; Thu Oct 21 22:33:23 -0400 2021
Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 91a1b393 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Thu, 21 Oct 2021 19:26:08 -0700 (PDT)
Message-ID: <50368F546EFF3B1F9DA141F1958AD62E@eigenstate.org>
To: 9front@9front.org
Date: Thu, 21 Oct 2021 22:26:06 -0400
From: ori@eigenstate.org
In-Reply-To: <3A3232C4C6B43DBA8D030707D5F546BA@5ess.inri.net>
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: component rails 
Subject: Re: [9front] intent to delete: devssl, cpu, oexportfs, import
Reply-To: 9front@9front.org
Precedence: bulk

Quoth sl@stanleylieber.com:
> > not used anywhere except for cpu(1), oexportfs(4), and
> > import(4).
> 
> so this change would mean 9front users can no longer cpu
> or import with plan 9 from bell labs or 9legacy machines?
> 
> sl

Correct.

I'd like to interoperate, but SSL3 is broken. I don't think
we should drag around broken protocols for eternity.

If you patch 9legacy's cpu listener to use devtls instead of
devssl, then the corresponding cpu(1) patch should be easy. 
I think this is the best option.