9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] no more auth in exportfs(4)?
Date: Fri, 01 Oct 2021 10:49:21 +0200	[thread overview]
Message-ID: <B7F17241E3B6F6FF70A2B1BEECE76B95@felloff.net> (raw)
In-Reply-To: <A72B92C315D464F7DE8A24581FA3CCAF@z0.is>

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

  reply	other threads:[~2021-10-01  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 19:32 me
2021-10-01  8:49 ` cinap_lenrek [this message]
2021-10-01  9:11   ` [9front] [PATCH] inherit the auth_chid to exportfs Josuah Demangeon
2021-10-02 19:55     ` cinap_lenrek
2021-10-03  9:36       ` sirjofri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B7F17241E3B6F6FF70A2B1BEECE76B95@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).