|
From: Hans B. <han...@gm...> - 2017-02-15 19:37:38
|
On 2017-02-14 9:11, Antonio SJ Musumeci wrote: > As the documentation mentions the option when enabled causes the > kernel to do the permission checks. IE... based on what has already > been returned to the kernel from getattr. If not enabled it's your > responsibility to manage checking of permissions. The kernel and FUSE > just pass the request to your code and if there is a permission issue > you should return -EPERM or -EACCES. Thanks, that helped a bit but not all the way :( I did read the documentation, but what effects it might have to omit this option is still unknown to me. All I know is that it seems to help to not use this option for some users experiencing access problem over e.g. Samba. But I am a bit reluctant to remove it by default unless I understand exactly what negative effects that would have. > > On Tue, Feb 14, 2017 at 2:47 PM, Hans Beckerus > <han...@gm... <mailto:han...@gm...>> 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. > > > > Thanks. > > Hans > Any one that could tell me if it should be ok to leave this out? > What is > the drawback by not using -odefault_permissions? > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > -- > fuse-devel mailing list > To unsubscribe or subscribe, visit > https://lists.sourceforge.net/lists/listinfo/fuse-devel > <https://lists.sourceforge.net/lists/listinfo/fuse-devel> > > |