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: <20171121122338.s5kzemsyrfmesc43@linux.intel.com>
Date:   Tue, 21 Nov 2017 14:23:38 +0200
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Thomas Gleixner <tglx@...utronix.de>
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, Nov 21, 2017 at 12:48:26AM +0100, Thomas Gleixner wrote:
> The launch enclave is part of the kernel, at least that's what the subject
> line claims. So why and how would it do a syscall? The kernel has it's
> internal crypto API.

It's part of the kernel in the way as lets say code arch/x86/realmode
is. It's hosted by kernel but it does not run in the same address space
as the kernel.

These constraints apply for enclaves:

1. They only run in ring-3.
2. They can only execute code inside their address range.

/Jarkko