Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp289958yba; Thu, 16 May 2019 00:26:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqywmtTyABdFxiehJjri7puWu6mueOOKq2MNwKSLDeDv2ZjYGMjKIpDofeG/Fo0uvIJ9GOeX X-Received: by 2002:a63:fa16:: with SMTP id y22mr9045684pgh.15.1557991591516; Thu, 16 May 2019 00:26:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557991591; cv=none; d=google.com; s=arc-20160816; b=eS1O/x32fxb0gfDzmwD5Ibf6nwQ/NtWGbMuun27rDH/1lqXHl27MXVxO1c8m2Mq7jL tNilMRwRDNc91G30wSfYzWNtap2zjMG2NrufXbrLZ1Hf8UW/GQGC5bzdzEEvDO5tNhCH IuaA2W7m0b0WlDeia2FEsLhTNccQNz9ba862LyzXrgzv8RpMcGa60DaX5xIHv7sxnj8x kjTb09m9SV7kzvi1S30b+h8aGFOydXl/dxU3lF2VUlN2TlDns1TgRGT1Dw0Yq4wQ2Q7R Mmu5VubvXv/6TAmTn55TKg4sBFsNDTGjlixjpvR9AQIW8qVxtOjwQoTj7tjo2GUDHKRQ NWEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=DviWeXD3BxiR+8a9BTZbnB29GJqT0qUkok9x0i3NBMg=; b=BxDX85iHUEVBX+JgJxqzNyIJ3OmQ2cFqJzPFbtWbvEng2AQZyCJG44cNLUJmYtLbu/ oaf8fEQfrxYSri0lPav65y1W4e9QIkksHWzZvy67jKI6dzvPZFnvCgY1duHwqFzk8JMQ ravgcynwUqOqKvfO95HJwcYdd953PcgsdT/MceO3/Cwguw8WVi4hp0fweTqwar9hvrep j8qt715pEb/3FjLeRC2V69g4j+E2riQUYTERzXMOoGCtMWI7/CrB6e0QZicpAMC9Vqfi zdeWOG8QplDuHn4tlAKUsiUiiTY8qG/TrQLzxnbH+hr+vCJQQfb4G+eTy5VH/C8YqOzn p8Mg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l6si3961639pgp.382.2019.05.16.00.26.15; Thu, 16 May 2019 00:26:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726638AbfEPHZK (ORCPT + 99 others); Thu, 16 May 2019 03:25:10 -0400 Received: from namei.org ([65.99.196.166]:39464 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726277AbfEPHZK (ORCPT ); Thu, 16 May 2019 03:25:10 -0400 Received: from localhost (localhost [127.0.0.1]) by namei.org (8.14.4/8.14.4) with ESMTP id x4G7OX82023904; Thu, 16 May 2019 07:24:33 GMT Date: Thu, 16 May 2019 17:24:33 +1000 (AEST) From: James Morris To: Andy Lutomirski cc: Sean Christopherson , "Serge E. Hallyn" , LSM List , Paul Moore , Stephen Smalley , Eric Paris , selinux@vger.kernel.org, Jarkko Sakkinen , Jethro Beekman , "Xing, Cedric" , "Hansen, Dave" , Thomas Gleixner , "Dr. Greg" , Linus Torvalds , LKML , X86 ML , "linux-sgx@vger.kernel.org" , Andrew Morton , "nhorman@redhat.com" , "npmccallum@redhat.com" , "Ayoun, Serge" , "Katz-zamir, Shay" , "Huang, Haitao" , Andy Shevchenko , "Svahn, Kai" , Borislav Petkov , Josh Triplett , "Huang, Kai" , David Rientjes Subject: Re: SGX vs LSM (Re: [PATCH v20 00/28] Intel SGX1 support) In-Reply-To: Message-ID: References: <8fe520bb-30bd-f246-a3d8-c5443e47a014@intel.com> <358e9b36-230f-eb18-efdb-b472be8438b4@fortanix.com> <960B34DE67B9E140824F1DCDEC400C0F4E886094@ORSMSX116.amr.corp.intel.com> <6da269d8-7ebb-4177-b6a7-50cc5b435cf4@fortanix.com> <20190513102926.GD8743@linux.intel.com> <20190514104323.GA7591@linux.intel.com> <20190514204527.GC1977@linux.intel.com> <20190515013031.GF1977@linux.intel.com> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 15 May 2019, Andy Lutomirski wrote: > On Wed, May 15, 2019 at 3:46 PM James Morris wrote: > > > > You could try user.sigstruct, which does not require any privs. > > > > I don't think I understand your proposal. What file would this > attribute be on? What would consume it? It would be on the enclave file, so you keep the sigstruct bound to it, rather than needing a separate file to manage. It would simplify any LSM policy check. It would be consumed by (I guess) the SGX_INIT_THE_ENCLAVE ioctl in your example, instead of having a 2nd fd. -- James Morris