Phillip Susi <[EMAIL PROTECTED]> writes:
> [ Should root be able to access everything? ]
BUGabundu is right, this discussion probably belongs somewhere else.
So let my just state my main point again: using --allow-root does not
have any negative side effects and would prevent many applications
from needing fixing.
> I believe the gvfs uses the kernel keyring for authentication to
> remote network resources and such, ergo simply being root can not
> grant you access.
gvfs does not need to be root in order for --allow-root to work. So
this shouldn't be a problem.
>> Changing the behavior to allowing root to stat() the directly (but not
>> granting read- or execute permissions) would probably also fix most of
>> the issues.
>
> Hrm.... it does seem like you should be able to stat the mount point
> itself. How would this solve the problem though? find often
> complains that it can't stat() temporary files that have been
> unlinked between the readdir() call and the stat(). Any calling
> script should not be upset by such errors.
Yes, but here the situation is different: readdir() returns an entry
that cannot be stat()ed. In the above case, we simply have a race
condition between stat() and readdir(). But this does not belong here
either, so I will try to get this change into FUSE.
Best,
-Nikolaus
--
»It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that.«
-J.H. Hardy
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
~/.gvfs causes various errors
https://bugs.launchpad.net/bugs/225361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
