From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Cyrus-Session-Id: sloti22d1t05-2906851-1522803411-2-10225222441739653425 X-Sieve: CMU Sieve 3.0 X-Spam-known-sender: no X-Spam-charsets: plain='UTF-8' X-Resolved-to: linux@kroah.com X-Delivered-to: linux@kroah.com X-Mail-from: linux-security-module-owner@vger.kernel.org ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm2; t= 1522803411; b=N1BnfZ8llR/n5qlVaR29b9cp8cRqfA1T0tS0kB7XFgviHIhNs7 dxJ2itzsRDRrxx+DtSCLUc9C24FIeKNXB78oLKgh9Q0GcWPctNMt+7ds9LPQx4aw OJKAdv9PMN8XLjGsMvZW/tGVjPiDo4Uuma/aVZxRhTqaXY2VGxEcT5whY2C4/RDp /4Xv34ZBcR1Dw+bOYeJeOmJWinDLACygCIG818TprfAJlTAm0yAZbBcPfeQUA6yI S7riFS3ArxX7uJIrjQCu5yfRgrnrjnHTchbaoSTh33a8T1bbyu/NuvIL145665g5 E1lQ9B8BQVuqsCtjXkoDosdXXFAxPrBAFtng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=mime-version:in-reply-to:references:from :date:message-id:subject:to:cc:content-type:sender:list-id; s= fm2; t=1522803411; bh=0T6/FliKJ+n2MWFpMpLJfcHabCgILu1YehuGPPUYQq Q=; b=NCUu9lr9Sie9ym4toHGSFuiHTTqfNPLtqdA/ObCLKnrffql9oRcCMELM6b IrmjNO0lokqHozBNz8w8aKPCPon6JbsNN0CKOriuzP9oD0IuqGMJbqm1yQdZlnum IfCNuYMOPvrhnwe6ivmO7BJdWjUwWFICmlh8EhyEY160uEojoO0AuK/lSvAMG/bi nFUPqbCDzsk8LCWWis7TRu/q+Ydk2fgh/cLkLICjNf25dcHI12MV42706RWGfhY2 EcrbXECqCtnRGyq2BVAI52p6hFDEKloOHeD83dLtxsZb/RU0NWAOP5FGLskWoT4G iob1j8s5rpHTHFQS+POxNvjF4qaQ== ARC-Authentication-Results: i=1; mx5.messagingengine.com; arc=none (no signatures found); dkim=fail (message has been altered, 1024-bit rsa key sha256) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=Q9AeUzqE x-bits=1024 x-keytype=rsa x-algorithm=sha256 x-selector=google; dkim=fail (message has been altered, 2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=M4UD+SN3 x-bits=2048 x-keytype=rsa x-algorithm=sha256 x-selector=20161025; dmarc=none (p=none,has-list-id=yes,d=none) header.from=linux-foundation.org; iprev=pass policy.iprev=209.132.180.67 (vger.kernel.org); spf=none smtp.mailfrom=linux-security-module-owner@vger.kernel.org smtp.helo=vger.kernel.org; x-aligned-from=fail; x-cm=none score=0; x-google-dkim=fail (message has been altered, 2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=DE2UwcS4; x-ptr=pass x-ptr-helo=vger.kernel.org x-ptr-lookup=vger.kernel.org; x-return-mx=pass smtp.domain=vger.kernel.org smtp.result=pass smtp_org.domain=kernel.org smtp_org.result=pass smtp_is_org_domain=no header.domain=linux-foundation.org header.result=pass header_is_org_domain=yes; x-vs=clean score=-100 state=0 Authentication-Results: mx5.messagingengine.com; arc=none (no signatures found); dkim=fail (message has been altered, 1024-bit rsa key sha256) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=Q9AeUzqE x-bits=1024 x-keytype=rsa x-algorithm=sha256 x-selector=google; dkim=fail (message has been altered, 2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=M4UD+SN3 x-bits=2048 x-keytype=rsa x-algorithm=sha256 x-selector=20161025; dmarc=none (p=none,has-list-id=yes,d=none) header.from=linux-foundation.org; iprev=pass policy.iprev=209.132.180.67 (vger.kernel.org); spf=none smtp.mailfrom=linux-security-module-owner@vger.kernel.org smtp.helo=vger.kernel.org; x-aligned-from=fail; x-cm=none score=0; x-google-dkim=fail (message has been altered, 2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=DE2UwcS4; x-ptr=pass x-ptr-helo=vger.kernel.org x-ptr-lookup=vger.kernel.org; x-return-mx=pass smtp.domain=vger.kernel.org smtp.result=pass smtp_org.domain=kernel.org smtp_org.result=pass smtp_is_org_domain=no header.domain=linux-foundation.org header.result=pass header_is_org_domain=yes; x-vs=clean score=-100 state=0 X-ME-VSCategory: clean X-CM-Envelope: MS4wfP2emZ4OKZf56/LawmjHBxqcft6wksGmU+5scfu6H4zCt9D4HW7CWKQbLrhq1w3jPk5yBmWyZcZFl0geJQ+x0DMaqFjQmNjeSVlfBM89j9U4uvKhhTrq J3XOiS18msdxXJu0v4vOMJZ8Mh7r8qIpJd3XTtXWRJm9APdV/lgRSQPpZXxPIn6u+JWrHvb2KpJFsaeVMnh3zF11HfYqUOAGvq5qtjboQmuAATSl25nFAuvb 4dk4Omsz/YSPZY4ML2Pn+A== X-CM-Analysis: v=2.3 cv=NPP7BXyg c=1 sm=1 tr=0 a=UK1r566ZdBxH71SXbqIOeA==:117 a=UK1r566ZdBxH71SXbqIOeA==:17 a=IkcTkHD0fZMA:10 a=Kd1tUaAdevIA:10 a=1XWaLZrsAAAA:8 a=VwQbUJbxAAAA:8 a=VJ32U7px_5mGT2n6YQIA:9 a=QEXdDO2ut3YA:10 a=x8gzFH9gYPwA:10 a=AjGcO6oz07-iQ99wixmX:22 X-ME-CMScore: 0 X-ME-CMCategory: none Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754806AbeDDA4s (ORCPT ); Tue, 3 Apr 2018 20:56:48 -0400 Received: from mail-io0-f195.google.com ([209.85.223.195]:44398 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754803AbeDDA4p (ORCPT ); Tue, 3 Apr 2018 20:56:45 -0400 X-Google-Smtp-Source: AIpwx4839QYyC50quuSyFza/LLjOI/9j++hvEwkY53cUhKvN06+x/xl8GjeTtNnQgyT+CLGmRVePRh5Ffqtirada2a8= MIME-Version: 1.0 In-Reply-To: References: <4136.1522452584@warthog.procyon.org.uk> <186aeb7e-1225-4bb8-3ff5-863a1cde86de@kernel.org> <30459.1522739219@warthog.procyon.org.uk> <9758.1522775763@warthog.procyon.org.uk> <13189.1522784944@warthog.procyon.org.uk> <9349.1522794769@warthog.procyon.org.uk> From: Linus Torvalds Date: Tue, 3 Apr 2018 17:56:43 -0700 X-Google-Sender-Auth: BO-Z0aaARvuvOjkSwGiK6AOPP1I Message-ID: Subject: Re: [GIT PULL] Kernel lockdown for secure boot To: Matthew Garrett Cc: Andrew Lutomirski , David Howells , Ard Biesheuvel , James Morris , Alan Cox , Greg Kroah-Hartman , Linux Kernel Mailing List , Justin Forbes , linux-man , joeyli , LSM List , Linux API , Kees Cook , linux-efi Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-security-module@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Tue, Apr 3, 2018 at 5:46 PM, Matthew Garrett wrote: > > The generic distros have been shipping this policy for the past 5 years. .. so apparently it doesn't actually break things? Why not enable it by default then? And if "turn off secure boot" really is the accepted - and actuially used - workaround for the breakage, then WHY THE HELL DIDN'T YOU START OFF BY EXPLAINING THAT IN THE FIRST PLACE WHEN PEOPLE ASKED WHY THE TIE-IN EXISTED? Sorry for shouting, but really. We have a thread of just *how* many email messages that asked for the explanation for this? All we got was incomprehensible and illogical crap explanations. If there actually was a good explanation for the tie-in, it should have been front-and-center and explained as such. Linus