From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E26BBF94 for ; Thu, 6 Sep 2018 10:22:00 +0000 (UTC) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9CAE18B for ; Thu, 6 Sep 2018 10:22:00 +0000 (UTC) From: Jani Nikula To: David Howells In-Reply-To: <17243.1536228343@warthog.procyon.org.uk> References: <87y3cfymgr.fsf@intel.com> <17533.1536166384@warthog.procyon.org.uk> <32341.1536178494@warthog.procyon.org.uk> <17243.1536228343@warthog.procyon.org.uk> Date: Thu, 06 Sep 2018 13:21:16 +0300 Message-ID: <87sh2nylib.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Cc: James Bottomley , joeyli.kernel@gmail.com, ksummit-discuss@lists.linuxfoundation.org, Justin Forbes , Peter Jones , Andy Lutomirski Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel lockdown and secure boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 06 Sep 2018, David Howells wrote: > Jani Nikula wrote: > >> I guess I'm asking, have you considered an audit log for lockdown >> blocked access, and if you've rejected the idea, why? > > It logs a message to dmesg telling you what caused the rejection. Ah, good. Looks like this was added at some point, and the user was running kernel lockdown without this. Thanks, Jani. -- Jani Nikula, Intel Open Source Graphics Center