linux-kernel - Re: [PATCH v5 1/3] create SMAF module

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: <CA+M3ks7xTRHFa30jT3180D1_EV=bEmb1Pk8d_A8PJbXnD0ddxg@mail.gmail.com>
Date:	Wed, 21 Oct 2015 17:34:36 +0200
From:	Benjamin Gaignard <benjamin.gaignard@...aro.org>
To:	James Morris <jmorris@...ei.org>
Cc:	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Rob Clark <robdclark@...il.com>,
	Thierry Reding <treding@...dia.com>,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Tom Cooksey <tom.cooksey@....com>,
	Daniel Stone <daniel.stone@...labora.com>,
	linux-security-module@...r.kernel.org,
	Xiaoquan Li <xiaoquan.li@...antecorp.com>,
	Laura Abbott <labbott@...hat.com>,
	Tom Gall <tom.gall@...aro.org>,
	Linaro MM SIG Mailman List <linaro-mm-sig@...ts.linaro.org>
Subject: Re: [PATCH v5 1/3] create SMAF module

2015-10-21 16:32 GMT+02:00 James Morris <jmorris@...ei.org>:
> On Wed, 21 Oct 2015, Benjamin Gaignard wrote:
>
>> Secure Memory Allocation Framework goal is to be able
>> to allocate memory that can be securing.
>> There is so much ways to allocate and securing memory that SMAF
>> doesn't do it by itself but need help of additional modules.
>> To be sure to use the correct allocation method SMAF implement
>> deferred allocation (i.e. allocate memory when only really needed)
>>
>> Allocation modules (smaf-alloctor.h):
>> SMAF could manage with multiple allocation modules at same time.
>> To select the good one SMAF call match() to be sure that a module
>> can allocate memory for a given list of devices. It is to the module
>> to check if the devices are compatible or not with it allocation
>> method.
>>
>> Securing module (smaf-secure.h):
>> The way of how securing memory it is done is platform specific.
>> Secure module is responsible of grant/revoke memory access.
>>
>
> This documentation is highly inadequate.

If you give hints I will try to complete it and make it acceptable.

>
> What does "allocate memory that can be securing" mean?

Maybe I could re-phrase it like that:
"Secure Memory Allocation Framework goal is to be able to allocate
memory that the platform can secure."

I'm trying to be generic here because each could have it own method to
secure buffers.

>
>
> --
> James Morris
> <jmorris@...ei.org>
>



-- 
Benjamin Gaignard

Graphic Working Group

Linaro.org │ Open source software for ARM SoCs

Follow Linaro: Facebook | Twitter | Blog
--
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/