From: Cord Seele <cord@seele.net>
To: fuse-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org
Subject: Bug: User can access dir while root can't?
Date: Wed, 18 May 2011 17:45:36 +0200 [thread overview]
Message-ID: <20110518154535.GV3676@t61p.seele.net> (raw)
Hello,
I encountered this strange behaviour and think this might be a bug (or at
least a vfs inconsistency). I've found a dir .gvfs in my home dir that i can
access as user but root fails with EACCES:
~> ls -dlin .gvfs
1 dr-x------ 2 1000 100 0 13. Mai 10:13 .gvfs
~> cd .gvfs
~/.gvfs> ls -lan
total 4
dr-x------ 2 1000 100 0 May 13 10:13 .
drwxr-xr-x 75 1000 100 4096 May 18 17:30 ..
~/.gvfs> cd ..
~> su
Passwort:
# ls -dlin .gvfs
ls: cannot access .gvfs: Permission denied
# cd .gvfs
bash: cd: .gvfs: Permission denied
~> mount|grep gvfs
gvfs-fuse-daemon on /home/cord/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,
nodev,relatime,user_id=1000,group_id=100)
My kernel is a 2.6.37.6 (from an OpenSUSE 11.4).
Is the access denial to root for this directory considered OK? I also wonder
about the reported dir size of zero (or is this normal for FUSE which I am not
familiar with).
Sorry for the noise, if this is all due to a misbehaving gvfs-fuse-daemon.
Thanks,
Cord
reply other threads:[~2011-05-18 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110518154535.GV3676@t61p.seele.net \
--to=cord@seele.net \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.