From: Szabolcs S. <sz...@nt...> - 2008-04-08 12:52:01
|
On Tue, 8 Apr 2008, Marc Andre Tanner wrote: > So when you want a fuse file system with correct permission semantics Not "a fuse file system". We were talking about only fusexmp. For example ntfs-3g passes all the tests but it doesn't use seteuid/setgid to achieve this. FUSE can be used in several ways, it's very flexible. Unfortunately this often results incorrect conclucions and generalizations about its capabilities and performance. One of the aims of the NTFS-3G project is exactly that that it refutes/adjusts such myths. Szaka > for multiple users you basically have to wrap every operation with: > > setegid(fuse_get_context()->gid); > seteuid(fuse_get_context()->uid); > /* do some work */ > seteuid(getuid()); > setegid(getgid()); > > Or am i missing something? But this only works when the file system is > mounted by root. Also are the euid, egid stored per thread? If not then > this will cause all kind of problems with race conditions. > > So in my opinion -o allow_other when used as a non root user and not > intended for read only access is basically useless because new files > will be owned by the user who mounted the fs. > > Cheers, > Marc > > -- NTFS-3G: http://ntfs-3g.org |