9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] notes on user none
Date: Mon, 1 Feb 2021 22:06:08 +0000 (UTC)	[thread overview]
Message-ID: <9c978b00-674a-4425-ab75-5c19a0d01b9b@sirjofri.de> (raw)
In-Reply-To: <861re06axf.fsf@cmarib.ramside>

Hello,

I think the system assumes that every user only has access to oneself. 
And since users are secure (glenda can't read my files) it makes sense to 
save the files of user none with user permissions. If none was handled 
like all other users this would effectively give away the security by 
using auth/none. Making the privileges for none like the world user gives 
all other users also the same privileges as the world user, which they 
basically already have (hence it's world).

Auth/none makes you none, but not authenticated. So it's like fake 
access. A nobody, a world user. No longer part of the system. You lose 
privilege.

I'm not saying it's the most elegant design. But try giving nobody access 
to a system that's basically built around user privileges. Try that 
without a user.

TLDR: it makes sense doing it like cwfs currently does and like described 
in the 9 paper. None shouldn't be seen as a user, more like batman, a 
symbol for everyone in the world. Therefore it needs different handling.

sirjofri

(Just my two cents. I'm not a Plan 9 veteran or 9front developer, only a 
user who cares.)

      reply	other threads:[~2021-02-02  1:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 23:44 Anthony Martin
2021-01-23  9:45 ` sirjofri
2021-01-23 14:02   ` hiro
2021-01-23 14:13 ` cinap_lenrek
2021-01-23 21:31 ` ori
2021-01-24  6:33   ` magma698hfsp273p9f
2021-01-25 19:44     ` ori
2021-01-31 21:42       ` magma698hfsp273p9f
2021-02-01 22:06         ` sirjofri [this message]

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=9c978b00-674a-4425-ab75-5c19a0d01b9b@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).