9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] user none: cwfs vs hjfs
Date: Fri, 22 Jan 2021 10:41:48 +0100	[thread overview]
Message-ID: <CAFSF3XOZPdM5yJ705U_1hPJW=r2rotx1DkVN90Eh+RdAR81d2A@mail.gmail.com> (raw)
In-Reply-To: <A3D46C22-70B4-4CA3-8D5E-9496A0DB9DB4@stanleylieber.com>

> upas becomes user none to process files through /mail/queue no
> matter who upas starts out running as.

sounds like a bug

> that has no current solution except "run everything that requires file
> privacy on separate file systems."

later on you say file permissions are granular enough. so i don't know
why you say here that "file privacy" would be a problem.

> but cannot be masked
> from the special # file system.

oh? i was not aware. do you have a trivial example for this, i'm curious!

> solution at all. any regular user must be trusted with proc, binding,
> unbinding, this is why user none exists in the first place.

> the disconnect here is between file and process permissions. they are
> completely different things. we have fine grained file permissions but auth
> is all or nothing.

so is there a problem with /proc ? can we read other user's memory or
something? or what did you find?

  parent reply	other threads:[~2021-01-22 10:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 20:16 Stanley Lieber
2021-01-19 20:36 ` hiro
2021-01-19 20:51 ` Silas McCroskey
2021-01-19 20:57   ` Silas McCroskey
2021-01-19 21:35     ` Stanley Lieber
2021-01-19 21:54       ` hiro
2021-01-19 21:58         ` Anthony Martin
2021-01-21 16:22           ` ori
2021-01-21 17:05             ` sirjofri
2021-01-21 17:36               ` Stanley Lieber
2021-01-21 22:01                 ` hiro
2021-01-21 22:15                   ` Stanley Lieber
2021-01-21 22:51                     ` hiro
2021-01-21 22:55                       ` hiro
2021-01-21 23:26                         ` Silas McCroskey
2021-01-21 23:55                           ` Stanley Lieber
2021-01-22  0:13                             ` Silas McCroskey
2021-01-23 15:08                               ` cinap_lenrek
2021-01-22  0:24                             ` ori
2021-01-22  0:53                               ` Stanley Lieber
2021-01-22  9:53                                 ` hiro
2021-01-22  0:10                           ` Anthony Martin
2021-01-21 23:44                         ` Stanley Lieber
2021-01-22  0:00                           ` Silas McCroskey
2021-01-22  9:14                           ` hiro
2021-01-22 14:51                             ` Stanley Lieber
2021-01-22 15:01                               ` hiro
2021-01-22 15:39                                 ` Stanley Lieber
2021-01-22  9:41                           ` hiro [this message]
2021-01-21 23:00                       ` Stanley Lieber
2021-01-21 23:08                         ` Stanley Lieber
2021-01-19 23:04         ` Silas McCroskey
2021-01-20  1:12           ` hiro
2021-01-20  1:50             ` Stanley Lieber
2021-01-19 21:07   ` Stanley Lieber

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='CAFSF3XOZPdM5yJ705U_1hPJW=r2rotx1DkVN90Eh+RdAR81d2A@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --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).