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 3925 invoked from network); 1 Oct 2021 08:59:49 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 1 Oct 2021 08:59:49 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Fri Oct 1 04:49:33 -0400 2021 Message-ID: Date: Fri, 01 Oct 2021 10:49:21 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: ISO-certified open package information solution Subject: Re: [9front] no more auth in exportfs(4)? Reply-To: 9front@9front.org Precedence: bulk the authentication removed here is *NOT* 9p authentication (using Tauth request) but the old import protocol that runs before the 9p phase. theres an oexportfs(4) that still has it, we just dont want to pollute exportfs with the legacy cruft. in rcpu/rimport, we do not need authentication at exportfs level, as tlssrv -9 does that phase (plus sets up encrypted channel), and after it, it is just normal 9p with authentication disabled. (exportfs is already running as the correct user). -- cinap