Re: [fuse-devel] mount option default_permissions

[Nikolaus R. <Nik...@ra...>]

On Feb 14 2017, Hans Beckerus <han...@pu...> wrote:
> On 2017-02-11 3:13, Hans Beckerus wrote:
>> Hello, my high-level file system has always enforced the use of the 
>> 'default_permissions' mount option.
>> Now I got several users reporting problems with mounts exported across 
>> e.g. network shares that behaves a bit odd.
>> It does not seem to help when using allow_other either. I have no 
>> specific permission checks in my code.
>> Would it still be safe to leave out default_permissions, because that 
>> seems to be the one things that helps most (if not all) users.
>
> Any one that could tell me if it should be ok to leave this out? What is 
> the drawback by not using -odefault_permissions?

Well, I believe even if you do not use allow_others, this means some
operations that would normally fail will now succeed (unless you
implement permission checks in your filesystem).

For example, with default_permissions even the mounting user can't
delete files from a directory with 0550 permissions. Without it, he'd be
able to do so unless your filesystem prevents it.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«