daniel.poelzleithner wrote:
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.]
I like this for access to the builtin metafiles (whose permissions should normally be determined not individually but pased on the plugin and its permissions, but what about files within file-directories? For them I think we need to allow sys_reiser4 to change the bits independently, and for apps that don't know how to distinguish the 2 bits, oh well, change one change the other.
What are your thoughts?
regards ~ Daniel
