linux-kernel - Re: [PATCH v5 11/11] intel

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: <383f2831-b703-62c5-bf05-a990ce25f863@fortanix.com>
Date:   Tue, 21 Nov 2017 16:27:45 -0800
From:   Jethro Beekman <jethro@...tanix.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Peter Zijlstra <peterz@...radead.org>,
        platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v5 11/11] intel_sgx: driver documentation

On 2017-11-21 16:10, Borislav Petkov wrote:
> On Tue, Nov 21, 2017 at 03:45:31PM -0800, Jethro Beekman wrote:
>> Boris & Peter: this key has nothing to do with "trust" or "security".
> 
> But with what? Why is the firmware at all involved then?

See http://www.spinics.net/lists/platform-driver-x86/msg13829.html under 
"Launch control". Essentially, firmware can make it so that user has no 
control over IA32_SGXLEPUBKEYHASHn value.

One comment on the documentation I linked:

 > +The BIOS can configure IA32_SGXLEPUBKEYHASHn MSRs before feature control
 > +register is locked.

This is not entirely accurate, hardware exists on the market today where 
IA32_SGXLEPUBKEYHASHn can't be configured, even by firmware. As 
mentioned in my previous email, I'd like to use said hardware.

Jethro Beekman

Download attachment "smime.p7s" of type "application/pkcs7-signature" (3994 bytes)