linux-kernel - Re: [PATCH v3 0/7] dma-buf: heaps: Add secure heap

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]

Date:   Wed, 13 Dec 2023 11:05:17 +0200
From:   Pekka Paalanen <ppaalanen@...il.com>
To:     Simon Ser <contact@...rsion.fr>
Cc:     Yong Wu <yong.wu@...iatek.com>, Rob Herring <robh+dt@...nel.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        christian.koenig@....com,
        Matthias Brugger <matthias.bgg@...il.com>,
        dri-devel@...ts.freedesktop.org, John Stultz <jstultz@...gle.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Jeffrey Kardatzke <jkardatzke@...gle.com>,
        Benjamin Gaignard <benjamin.gaignard@...labora.com>,
        Vijayanand Jitta <quic_vjitta@...cinc.com>,
        Nicolas Dufresne <nicolas@...fresne.ca>,
        jianjiao.zeng@...iatek.com, linux-media@...r.kernel.org,
        devicetree@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>,
        ckoenig.leichtzumerken@...il.com, linaro-mm-sig@...ts.linaro.org,
        linux-mediatek@...ts.infradead.org,
        Joakim Bech <joakim.bech@...aro.org>, tjmercier@...gle.com,
        linux-arm-kernel@...ts.infradead.org,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>,
        kuohong.wang@...iatek.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/7] dma-buf: heaps: Add secure heap

On Tue, 12 Dec 2023 16:36:35 +0000
Simon Ser <contact@...rsion.fr> wrote:

> Is there a chance to pick a better name than "secure" here?
> 
> "Secure" is super overloaded, it's not clear at all what it means from
> just the name. Something like "restricted" would be an improvement.
> 

My thoughts exactly. Every time I see "secure" used for something that
either gives you garbage, refuses to work, or crashes your whole machine
*intentionally* when you try to do normal usual things to it in
userspace (like use it for GL texturing, or try to use KMS writeback), I
get an unscratchable itch.

There is nothing "secure" from security perspective there for end users
and developers. It's just inaccessible buffers.

I've been biting my lip until now, thinking it's too late.


Thanks,
pq

Content of type "application/pgp-signature" skipped