9front - general discussion about 9front
 help / color / mirror / Atom feed
From: magma698hfsp273p9f@icebubble.org
To: 9front@9front.org
Subject: Re: [9front] notes on user none
Date: Sun, 31 Jan 2021 21:42:04 +0000	[thread overview]
Message-ID: <861re06axf.fsf@cmarib.ramside> (raw)
In-Reply-To: <0298936785AE322EABB8CBD08698D520@eigenstate.org> (ori@eigenstate.org's message of "Mon, 25 Jan 2021 11:44:13 -0800")

ori@eigenstate.org writes:

>> Um.  What if the file is owned by "none", but chmod 0400?  The u+r would
>> suggest that it would be readable.  But, if only world permissions are
>> checked, the o-r suggests that it would be be unreadable.
>
> Yes, that's the "not fooling yourself" part.
>
> if none checked permissions as normal, you could
> simply do
>
> 	auth/none cat file
>
> as any user. if none can read it, so can anyon else.

The point is taken, but shouldn't a file owned by none u+r be readable
by none?  I can see how one might fool oneself if a file owned by none
is chmod 0004.  "auth/none cat" can still read it.  But if it's chmod
0400, I would think it should be readable by none.  If you ONLY consult
the world permissions, you're still "fooling yourself"... just in the
opposite direction.

To me, it makes perfect sense for a file to be readable by none if any
of its user, group, or world permissions grant read permission.  That's
the way permissions normally work on Plan 9.  Creating an exception to
those (otherwise regular) rules seems like it's CREATING a way to fool
yourself.

  reply	other threads:[~2021-02-01 23:45 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 [this message]
2021-02-01 22:06         ` 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=861re06axf.fsf@cmarib.ramside \
    --to=magma698hfsp273p9f@icebubble.org \
    --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).