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=1.1 required=5.0 tests=DATE_IN_PAST_06_12 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 32470 invoked from network); 22 Oct 2021 10:14:51 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 22 Oct 2021 10:14:51 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 4ess; Thu Oct 21 23:00:01 -0400 2021 Received: from [127.0.0.1] ([166.175.185.133]) by 5ess; Thu Oct 21 22:44:34 -0400 2021 Date: Fri, 22 Oct 2021 02:44:32 +0000 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <50368F546EFF3B1F9DA141F1958AD62E@eigenstate.org> References: <50368F546EFF3B1F9DA141F1958AD62E@eigenstate.org> Message-ID: <9AD80C9F-D44F-40CF-AF8A-91026FB7416A@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: responsive hypervisor-aware dependency control Subject: Re: [9front] intent to delete: devssl, cpu, oexportfs, import Reply-To: 9front@9front.org Precedence: bulk On October 22, 2021 2:26:06 AM UTC, ori@eigenstate=2Eorg wrote: >Quoth sl@stanleylieber=2Ecom: >> > not used anywhere except for cpu(1), oexportfs(4), and >> > import(4)=2E >>=20 >> so this change would mean 9front users can no longer cpu >> or import with plan 9 from bell labs or 9legacy machines? >>=20 >> sl > >Correct=2E > >I'd like to interoperate, but SSL3 is broken=2E I don't think >we should drag around broken protocols for eternity=2E > >If you patch 9legacy's cpu listener to use devtls instead of >devssl, then the corresponding cpu(1) patch should be easy=2E=20 >I think this is the best option=2E > > just wanted to makes sure this was clear for viewers watching at home=2E sl