From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] user none: cwfs vs hjfs
Date: Tue, 19 Jan 2021 21:36:10 +0100 [thread overview]
Message-ID: <CAFSF3XN0Gj9hUBnnr2oiCFz9atrn812WWEuZp1sM_2daBeWm3Q@mail.gmail.com> (raw)
In-Reply-To: <2A888CF9-DEBE-4DFF-A68D-0EE4086EA8A5@stanleylieber.com>
cpu% date > blabla; ls -l blabla; auth/none cat blabla
--rw-r--r-- M 3288 hiro hiro 29 Jan 19 21:34 blabla
Tue Jan 19 21:34:07 CET 2021
cwfs manpage has:
The group numbered 9999, normally called noworld, is special
on the file server. Any user belonging to that group has
attenuated access privileges. Specifically, when checking
such a user's access to files, the file's permission bits
are first ANDed with 0770 for normal files or 0771 for
directories. The effect is to deny world access permissions
to noworld users, except when walking directories.
but i don't know how to check if none is part of noworld group...?
On 1/19/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> can someone with a working cwfs install please verify that user none is
> unable to access files (even user none g+rw) unless they are world
> readable?
>
> hjfs allows user none to access files that are not world readable.
>
> thanks,
>
> sl
>
next prev parent reply other threads:[~2021-01-19 21:04 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 [this message]
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
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=CAFSF3XN0Gj9hUBnnr2oiCFz9atrn812WWEuZp1sM_2daBeWm3Q@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).