From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: [PATCH v17 18/23] platform/x86: Intel SGX driver Date: Tue, 20 Nov 2018 14:04:42 +0200 Message-ID: <20181120120442.GA22172@linux.intel.com> References: <20181116010412.23967-1-jarkko.sakkinen@linux.intel.com> <20181116010412.23967-19-jarkko.sakkinen@linux.intel.com> <20181119161917.GF13298@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski Cc: X86 ML , Platform Driver , linux-sgx@vger.kernel.org, Dave Hansen , "Christopherson, Sean J" , nhorman@redhat.com, npmccallum@redhat.com, "Ayoun, Serge" , shay.katz-zamir@intel.com, haitao.huang@linux.intel.com, Andy Shevchenko , Thomas Gleixner , "Svahn, Kai" , mark.shanahan@intel.com, Suresh Siddha , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Darren Hart , andy@infradead.org, LKML List-Id: platform-driver-x86.vger.kernel.org On Mon, Nov 19, 2018 at 08:59:24AM -0800, Andy Lutomirski wrote: > The idea here is that, under normal circumstances, provisioning only > runs once, or at least only runs rarely. So, rather than the SDK > running provisioning whenever it feels like doing so (which is the > current behavior, I imagine, although I haven't looked), there would > be a privileged program, perhaps a systemd unit that runs when needed, > that produces the key material needed for remote attestation, and > non-root users that need attestation would get the keying material > from the provisioning service. And the provisioning service could > implement its own policy. Ideally, the service wouldn't give the > sealed keys to users at all but would, instead, just provide the > entire attestation service over a UNIX socket, which would make > provisioning capabilities revocable. > > Does this make sense? Yes, it does for me at least now that you brought some context. /Jarkko