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.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 1392 invoked from network); 22 Oct 2021 10:26:59 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 22 Oct 2021 10:26:59 -0000 Received: from mail-4316.protonmail.ch ([185.70.43.16]) by 4ess; Fri Oct 22 06:20:12 -0400 2021 Date: Fri, 22 Oct 2021 10:19:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1634898001; bh=jvlV+12Ks48Ny7t4224AMo1WG40nPgA35bUScIrxAvw=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From; b=L3HNLJd5kzOmWc188TJmFXEHg9Ns60G9HsK13Fed9y85ouphLBy5kJbEIh1co8xPN cXoBjjtKE8qndHhIdpQbiUp2qHlJwj97k9OKCw15ifSZRGKoAEtPPQiLG8Adobo6QC 8W44MW28mzE+1r7gf94jkr+4dh/o3f/kGEwFdklk= To: 9front@9front.org From: Philip Silva Message-ID: In-Reply-To: <9AD80C9F-D44F-40CF-AF8A-91026FB7416A@stanleylieber.com> References: <50368F546EFF3B1F9DA141F1958AD62E@eigenstate.org> <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: module core-based database information framework Subject: Re: [9front] intent to delete: devssl, cpu, oexportfs, import Reply-To: 9front@9front.org Precedence: bulk That would be a pity to remove interoperability although SSL 3.0 is probabl= y not so good. But I wonder, isn't it possible to just remove the SSL 3.0? = Also in the patch list of 9legacy, there seems to be a set of patches for T= LS 1.2 for devtls. Not knowing so much about the internals anyway, I though= t that cpu'ing (or at least drawterm'ing) to 9legacy was unencrypted anyway= .