linux-kernel - Re: [PATCH v12 00/18] Enable FSGSBASE instructions

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: <39df26f2-9d17-b0f2-6a55-48195542637b@cs.unc.edu>
Date:   Thu, 28 May 2020 13:37:27 -0400
From:   Don Porter <porter@...unc.edu>
To:     Sasha Levin <sashal@...nel.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Andi Kleen <ak@...ux.intel.com>, linux-kernel@...r.kernel.org,
        bp@...en8.de, luto@...nel.org, hpa@...or.com,
        dave.hansen@...el.com, tony.luck@...el.com,
        ravi.v.shankar@...el.com, chang.seok.bae@...el.com
Subject: Re: [PATCH v12 00/18] Enable FSGSBASE instructions

On 5/26/20 6:51 PM, Sasha Levin wrote:
> On Tue, May 26, 2020 at 06:03:35PM -0400, Don Porter wrote:
>> On 5/26/20 4:27 PM, Sasha Levin wrote:
>>> I'm really worried about the disconnect between how you view the current
>>> state of Graphene (and the industry) vs Intel and the various cloud
>>> providers.
>>>
> 
> Sorry, I wasn't trying to suggest that all cloud vendors are pushing
> Graphene, but rather than SGX enabled platforms became a commodity
> product, users will end up using Graphene-like applications.
> 
> Let me provide an example:
> https://www.alibabacloud.com/blog/protecting-go-language-applications-with-the-graphene-library-os-on-intel%C2%AE-sgx%C2%AE-secured-alibaba-cloud_594889 
> 
> - a "practical" guide on how to run Graphene in production environment
>    on one of the big cloud vendor platforms.

You have convinced me there is a concerning disconnect here, and we need 
to be proactive as a project to correct this.  We are adding warnings to 
the project with all due haste.