From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] user none: cwfs vs hjfs
Date: Thu, 21 Jan 2021 16:24:05 -0800 [thread overview]
Message-ID: <8810E8F846CEF25EEA2C33E9D750FA3D@eigenstate.org> (raw)
In-Reply-To: <8D8FC1E6-517F-4265-A250-55A8C990477C@stanleylieber.com>
Quoth Stanley Lieber <sl@stanleylieber.com>:
> On January 21, 2021 6:26:27 PM EST, Silas McCroskey <inkswinc@gmail.com> wrote:
> >> right now, running as user none is the only way to mask proc and other # file system data.
> >
> >How so?
> >
> >RFNOMNT If set, subsequent mounts into the new name space
> > and dereferencing of pathnames starting with # are
> > disallowed.
> >
> >- sam-d
> >
>
> let's stipulate i don't know what i'm talking about.
>
> when i brought this up with cinap and ori on irc they agreed there is a bit of a problem here. maybe we're all wrong, or maybe i misunderstood their confirmation of my observations.
>
> observed: hjfs handles user none differently.
Yes. Let's normalize the behavior. Since it seems
like the cwfs behavior is expected and intended,
I'd want to patch hjfs to match it.
I'm happy to give you (and anyone else following)
time to fix bugs, maybe going as far as putting
the change behind a console knob for a few weeks
for testing. I'd want the knob to go away quickly,
though.
> observed: as a regular user i was able to access # after rfork m.
That is unexpected -- rfork m works as documented for me,
though I think we punched a couple of holes to make it
more useful. Without '#|', rc would be entirely broken
after 'rfork m'.
cpu% rfork m
cpu% for(d in `{awk '{print $1}' /dev/drivers}){
ls $d>/dev/null && echo allowed: $d
}
ls: #/: mount/attach disallowed
allowed: #c
ls: #¶: mount/attach disallowed
ls: #P: mount/attach disallowed
ls: #$: mount/attach disallowed
allowed: #e
allowed: #|
allowed: #p
ls: #M: mount/attach disallowed
ls: #s: mount/attach disallowed
ls: #σ: mount/attach disallowed
allowed: #d
ls: #r: mount/attach disallowed
ls: #D: mount/attach disallowed
ls: #a: mount/attach disallowed
ls: #¤: mount/attach disallowed
ls: #K: mount/attach disallowed
ls: #k: mount/attach disallowed
ls: #l: mount/attach disallowed
ls: #B: mount/attach disallowed
ls: #I: mount/attach disallowed
ls: #i: mount/attach disallowed
ls: #m: mount/attach disallowed
ls: #b: mount/attach disallowed
ls: #v: mount/attach disallowed
ls: #S: mount/attach disallowed
ls: #æ: mount/attach disallowed
ls: #A: mount/attach disallowed
ls: #t: mount/attach disallowed
ls: #u: mount/attach disallowed
ls: #g: mount/attach disallowed
ls: #X: mount/attach disallowed
ls: #Δ: mount/attach disallowed
On the other hand:
cpu% auth/none
cpu% for(d in `{awk '{print $1}' /dev/drivers}){
ls $d>/dev/null && echo allowed: $d
}
allowed: #/
allowed: #c
allowed: #¶
allowed: #P
allowed: #$
allowed: #e
allowed: #|
allowed: #p
ls: #M: mount/attach disallowed
allowed: #s
allowed: #σ
allowed: #d
allowed: #r
allowed: #D
allowed: #a
allowed: #¤
allowed: #K
allowed: #k
allowed: #l
allowed: #B
allowed: #I
ls: #i: no frame buffer
allowed: #m
ls: #b: permission denied
allowed: #v
allowed: #S
allowed: #æ
ls: #A: no free devices
allowed: #t
allowed: #u
allowed: #g
allowed: #X
allowed: #Δ
next prev parent reply other threads:[~2021-01-22 0:48 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 [this message]
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
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=8810E8F846CEF25EEA2C33E9D750FA3D@eigenstate.org \
--to=ori@eigenstate.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).