linux-kernel - Re: [PATCH v5 08/11] intel_sgx: in-kernel launch enclave

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: <alpine.DEB.2.20.1711202334030.2348@nanos>
Date:   Mon, 20 Nov 2017 23:43:22 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
cc:     Peter Zijlstra <peterz@...radead.org>,
        platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 08/11] intel_sgx: in-kernel launch enclave

On Tue, 21 Nov 2017, Jarkko Sakkinen wrote:
> On Wed, Nov 15, 2017 at 12:50:06PM +0100, Peter Zijlstra wrote:
> > On Mon, Nov 13, 2017 at 09:45:25PM +0200, Jarkko Sakkinen wrote:
> > > TinyCrypt (https://github.com/01org/tinycrypt) is used as AES
> > > implementation, which is not timing resistant. Eventually this needs to
> > > be replaced with AES-NI based implementation that could be either
> > 
> > > - re-use existing AES-NI code in the kernel
> > 
> > This. That is an absolute must. We're not going to merge custom AES
> > implementations.
> 
> I'll post v6 update without update to this in order to get otherwise
> improved version out and work on it for v7.
> 
> My initial idea to sort this out would be to try to compile
> 
>   arch/x86/crypto/aesni-intel_asm.S
> 
> as part of the enclave binary and use it to run AES-256.

No. The kernel has a crypto API.

Thanks,

	tglx