From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 29212] noexec on file level (acl)
Date: Wed, 16 Feb 2011 15:02:21 GMT [thread overview]
Message-ID: <201102161502.p1GF2LGA032643@demeter1.kernel.org> (raw)
In-Reply-To: <bug-29212-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=29212
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #1 from Theodore Tso <tytso@mit.edu> 2011-02-16 15:02:19 ---
You can already turn off execute permission either using traditional Unix
permissions or via the current, existing ACL facility.
Note that it's actually pretty hard to stop a user from executing a file, since
it only requires one file system that is mounted w/o noexec, and then they can
simply copy the file (assuming they have read access) from its original
location to a location in their home directory, or /tmp perhaps, and execute it
there.
So it would first be useful if you were to describe exactly what your high
level goal is with having more fine-grained noexec capability. What are you
trying to do?
--
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 prev parent reply other threads:[~2011-02-16 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:03 [Bug 29212] New: noexec on file level (acl) bugzilla-daemon
2011-02-16 15:02 ` bugzilla-daemon [this message]
2011-02-16 15:35 ` [Bug 29212] " bugzilla-daemon
2011-02-16 18:20 ` bugzilla-daemon
2011-02-16 18:56 ` 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=201102161502.p1GF2LGA032643@demeter1.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).