From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 36312] New: User belonging to another Group has no access when chmod 0040
Date: Tue, 31 May 2011 00:19:20 GMT [thread overview]
Message-ID: <bug-36312-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=36312
Summary: User belonging to another Group has no access when
chmod 0040
Product: File System
Version: 2.5
Kernel Version: 2.6.39
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: ubuntuefnet@gmail.com
Regression: Yes
This may not be a bug, this may be intentional - however it was considered
pretty damn weird when encountered and worth a mention.
Say we have user 'bob', he is the owner of file 'accounting.txt' and
'accounting.txt' has group 'staff' attributed to the file which 'bob' is a part
of. If the permissions for the file only have group perms (e.g 0060), 'bob'
will not be able to access 'accounting.txt', however all other users in the
'staff' group will have access.
Replication via CLI:
touch myfile.txt && chown `whoami`:`groups | awk '{print $2}'` myfile.txt &&
chmod 0040 myfile.txt && cat myfile.txt
System: Debian 6.0.1
Arch: x86_64
Kernel: 2.6.39
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-05-31 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 0:19 bugzilla-daemon [this message]
2011-05-31 18:43 ` [Bug 36312] User belonging to another Group has no access when chmod 0040 bugzilla-daemon
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=bug-36312-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).