From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] user none: cwfs vs hjfs
Date: Tue, 19 Jan 2021 22:54:30 +0100 [thread overview]
Message-ID: <CAFSF3XMKJCD_4QgYT+TbUO1mad+2Xkqm69wuWUHEqw81iK+_=Q@mail.gmail.com> (raw)
In-Reply-To: <5AEC3297-201A-46C2-9B80-F5471F80EF26@stanleylieber.com>
i was under the impression that cwfs, like hjfs, wrongly allows
access. do notice that the cat in my example succeeds and prints date.
it shouldn't IMO.
On 1/19/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> On January 19, 2021 3:57:29 PM EST, Silas McCroskey <inkswinc@gmail.com>
> wrote:
>>ah, missed the "owned by user none g+rw" part.
>>
>>Same behavior:
>>
>>mystia% ls -ld /usr/none/incoming
>>d-rwxrwx--- M 5300 none ftp 0 Nov 15 2016 /usr/none/incoming
>>mystia% auth/none ls -l /usr/none/incoming
>>ls: /usr/none/incoming: '/usr/none/incoming' access permission denied
>>mystia% auth/none chmod 0777 /usr/none/incoming
>>mystia% auth/none touch /usr/none/incoming/file
>>mystia% auth/none chmod 0770 /usr/none/incoming/file
>>mystia% auth/none cat /usr/none/incoming/file
>>cat: can't open /usr/none/incoming/file: '/usr/none/incoming/file'
>>access permission denied
>>mystia%
>>
>>- sam-d
>>
>>On Tue, Jan 19, 2021 at 12:51 PM Silas McCroskey <inkswinc@gmail.com>
>> wrote:
>>>
>>> mystia% auth/none cat /usr/glenda/secstore
>>> cat: can't open /usr/glenda/secstore: '/usr/glenda/secstore' access
>>> permission denied
>>> mystia% auth/none ls -l /usr/glenda/priv/
>>> ls: /usr/glenda/priv/: '/usr/glenda/priv/' access permission denied
>>> mystia%
>>>
>>> anything more specific to try out?
>>>
>>> - sam-d
>>
>
> i first noticed this discrepancy back when i was first screwing around with
> /mail/queue; i mentioned it, but nobody was interested. hjfs just honors
> normal file permissions. at the very least, shouldn't all our file systems
> treat user none the same way?
>
> sl
>
next prev parent reply other threads:[~2021-01-19 22:19 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 [this message]
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='CAFSF3XMKJCD_4QgYT+TbUO1mad+2Xkqm69wuWUHEqw81iK+_=Q@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).