linux-kernel - Re: [kernel-hardening] [PATCH 1/1] Sealable memory support

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: <b3b4a71a-01a4-dad2-8df4-8b945c25be2f@huawei.com>
Date:   Mon, 22 May 2017 22:45:26 +0300
From:   Igor Stoppa <igor.stoppa@...wei.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     <mhocko@...nel.org>, <dave.hansen@...el.com>, <labbott@...hat.com>,
        <linux-mm@...ck.org>, <kernel-hardening@...ts.openwall.com>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [kernel-hardening] [PATCH 1/1] Sealable memory support

On 20/05/17 11:51, Greg KH wrote:
> On Fri, May 19, 2017 at 01:38:11PM +0300, Igor Stoppa wrote:
>> Dynamically allocated variables can be made read only,

[...]

> This is really nice, do you have a follow-on patch showing how any of
> the kernel can be changed to use this new subsystem?

Yes, actually I started from the need of turning into R/O some data
structures in both LSM Hooks and SE Linux.

> Without that, it
> might be hard to get this approved (we don't like adding new apis
> without users.)

Yes, I just wanted to give an early preview of the current
implementation, since it is significantly different from what I
initially proposed. So I was looking for early feedback.

Right now, I'm fixing it up and adding some more structured debugging.

Then I'll re-submit it together with the LSM Hooks example.

---
thanks, igor