linux-ext4 - [Bug 29212] noexec on file level (acl)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201102161502.p1GF2LGA032643@demeter1.kernel.org>
Date:	Wed, 16 Feb 2011 15:02:21 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 29212] noexec on file level (acl)

https://bugzilla.kernel.org/show_bug.cgi?id=29212

Theodore Tso <tytso@....edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #1 from Theodore Tso <tytso@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html