Thread (11 messages) 11 messages, 2 authors, 2018-03-07

[PATCH v4 1/3] security: Refactor LSM hooks into an array and enum

From: Sargun Dhillon <hidden>
Date: 2018-03-07 19:19:01
Also in: lkml

On Wed, Mar 7, 2018 at 9:45 AM, Casey Schaufler [off-list ref] wrote:
On 3/6/2018 11:23 PM, Sargun Dhillon wrote:
quoted
This commit should have no functional change. It changes the security hook
list heads struct into an array. Additionally, it exposes all of the hooks
via an enum. This loses memory layout randomization as the enum is not
randomized.
Please explain why you want to do this. I still dislike it.
Do you dislike it because of the loss of randomization, or some other reason?
The reason for not just having a second list_heads is that it's
somewhat ugly having to replicate that structure twice -- once for
dynamic hooks, and once for 'static' hooks.
Instead, we have one enum that LSMs can use and two arrays of heads
rather than an entire unrolled set of list_heads.

If we had a way to randomize this, would it make you comfortable?
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help