From: "daniel.poelzleithner" <poelzi@poelzi.org>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: Paul Wagland <paul@kungfoocoder.org>,
evilninja <evilninja@gmx.net>,
reiserfs-list@namesys.com, Hans Reiser <reiser@namesys.com>
Subject: Re: EACCESS vs ENOENT for nonexistent files-within-files
Date: Wed, 15 Sep 2004 18:15:21 +0200 [thread overview]
Message-ID: <41486A99.7050204@poelzi.org> (raw)
In-Reply-To: <16712.21927.550122.367489@thebsh.namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nikita Danilov wrote:
| > attributes? Even if the file is world readable? Does this really
make sense?
|
| To make things clear: I have described in my message how things actually
| do work in reiser4, so I don't see the point of your questions. If you
| think reiser4 semantics is wrong (I am not happy with it too, by the
| way), propose to Namesys something better.
I would suggest to allow lookups when the user can read the file. The x
bit should remain for exec on file objects, because console would be
pain when every file must have a exec bits to access meta data.
When the user can read a file, i don't think that the meta data can be
security risk, he has already access to the file.
And therefor not write access to file/metas without +w.
No, its not perfect, but i think more unix like than +x for lookups on
files.
regards
~ Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBSGqZy/mkIQp7AD0RAotiAKCTmffDuqsYj2KGkRtaE+fitU2e/QCfXS5t
qZHo5nFd0m1wJFw7MNhDTX8=
=Ejyo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-15 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 13:18 EACCESS vs ENOENT for nonexistent files-within-files Paul Wagland
2004-09-15 14:04 ` Hans Reiser
2004-09-15 14:16 ` Paul Wagland
2004-09-15 15:12 ` Nikita Danilov
2004-09-15 14:45 ` Nikita Danilov
2004-09-15 16:15 ` daniel.poelzleithner [this message]
2004-09-15 22:40 ` Hans Reiser
2004-09-16 19:55 ` Toby Dickenson
[not found] ` <2f9ccaae04091615395cfd0730@mail.gmail.com>
2004-09-16 22:40 ` Perry Kundert
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 14:06 Joe Orton
2004-09-13 14:25 ` Wayne Scott
2004-09-13 15:21 ` Michael Weissenbacher
2004-09-13 16:13 ` Alex Zarochentsev
2004-09-13 18:52 ` Joe Orton
2004-09-13 19:44 ` Nikita Danilov
2004-09-15 10:55 ` evilninja
2004-09-15 11:41 ` Nikita Danilov
2004-09-16 0:00 ` evilninja
2004-09-13 20:58 ` Alex Zarochentsev
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=41486A99.7050204@poelzi.org \
--to=poelzi@poelzi.org \
--cc=evilninja@gmx.net \
--cc=nikita@clusterfs.com \
--cc=paul@kungfoocoder.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.