From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] user none: cwfs vs hjfs
Date: Thu, 21 Jan 2021 17:15:41 -0500 [thread overview]
Message-ID: <84C199F8-15A4-4434-AD56-A35AB5CC6F4A@stanleylieber.com> (raw)
In-Reply-To: <CAFSF3XMA8MW8JHzNCKzJjqi236Jm6cHB30BpMx9fs4vzMHBarw@mail.gmail.com>
On January 21, 2021 5:01:06 PM EST, hiro <23hiro@gmail.com> wrote:
>otoh not fixing hjfs may break security assumptions.
>
yes. i think we should fix hjfs. a lot of stuff relies on user none doing what it does in cwfs. the most import thing is that all file systems behave the same way.
that said, relegating user none to world readable files while simultaneously running basically every service as none makes isolating services, and more blatantly keeping local users out of service files, difficult if not impossible.
i think they got lazy with user none. we need some finer grade control over user capabilities.
sl
next prev parent reply other threads:[~2021-01-21 22:44 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 [this message]
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
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=84C199F8-15A4-4434-AD56-A35AB5CC6F4A@stanleylieber.com \
--to=sl@stanleylieber.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).