linux-kernel - Re: [patch 0/4] MAP_NOZERO v2 - VM_NOZERO/MAP

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: <20070702190043.GN9157@hexapodia.org>
Date:	Mon, 2 Jul 2007 12:00:43 -0700
From:	Andy Isaacson <adi@...apodia.org>
To:	Kyle Moffett <mrmacman_g4@....com>
Cc:	Davide Libenzi <davidel@...ilserver.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Rik van Riel <riel@...hat.com>
Subject: Re: [patch 0/4] MAP_NOZERO v2 - VM_NOZERO/MAP_NOZERO early summer madness

On Sat, Jun 30, 2007 at 08:21:52PM -0400, Kyle Moffett wrote:
> That's why you'd need to call an LSM hook to get a unique identifier,  
> as the LSM would actually need to allocate identifiers for  
> equivalence classes.  Secondly, processes may change labels as they  
> run, so you couldn't just call it once and cache the result, you  
> would need to call it for every freed page (or every re-use of a page).

Davide's patch adds a owner_uid field to mm_struct.  Assuming that turns
into a "mm security equivalence class identifier", the LSM can simply
update it when a label-change-event occurs.  No need to call out to
(potentially heavyweight!) LSM code in page allocation critical paths.

I'm a bit concerned that tracking the equivalence classes will get
expensive.  I think you can end up with quadratic explosion in the worst
case (every user using every permutation of LSM bits).

-andy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/