From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E655EC433FE for ; Wed, 2 Nov 2022 00:53:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229871AbiKBAxH (ORCPT ); Tue, 1 Nov 2022 20:53:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229742AbiKBAxE (ORCPT ); Tue, 1 Nov 2022 20:53:04 -0400 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2F2F71C103; Tue, 1 Nov 2022 17:53:04 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id 60BE4CE1EFC; Wed, 2 Nov 2022 00:53:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3489AC433D6; Wed, 2 Nov 2022 00:53:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1667350380; bh=zU98Qd6nUGmbsVpz/zaMgp0xzDyYsHdeE2cMqaZDK34=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=ZD0XIW5X8bQ6GyxVaAkhMLCWAlzm9VPmO9F5d8uUJpE9qniKStI1ZrS29WoVjQbpB 5GeUbvC2XxFg5wVqqXuOnTx9fUIrnG/YN6LEWIp6v5VADmsmsO8IRMw4LBYxlLEYzj /LStFFZ1y8MApwlitOfYWxqWmfWz+OmglIGAOEuMrCMCIv7B3OJaieOjd8C0yxOL/l BDXaLuHWTOlj5aYuqa/2zY5l14+5Pg5CO61eq9q9HgQC/UjEPxyR7y70csFJ+slmPy 0mMRf484UAAkDBxY0meN6Dp7wdo2WfMjxO5031RS6JCkPVhdDPg5n53RmTuYYQ2JV6 aDuUf08k/3k1g== Date: Tue, 01 Nov 2022 17:52:58 -0700 From: Kees Cook To: Casey Schaufler , Kees Cook , Paul Moore CC: James Morris , "Serge E. Hallyn" , linux-security-module@vger.kernel.org, =?ISO-8859-1?Q?Micka=EBl_Sala=FCn?= , linux-kernel@vger.kernel.org, bpf@vger.kernel.org, linux-hardening@vger.kernel.org, casey@schaufler-ca.com Subject: Re: [PATCH v2] LSM: Better reporting of actual LSMs at boot User-Agent: K-9 Mail for Android In-Reply-To: References: <20221102000525.gonna.409-kees@kernel.org> Message-ID: <970317F3-D1A2-412D-88EF-18A606AC1E6A@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On November 1, 2022 5:46:55 PM PDT, Casey Schaufler wrote: >On 11/1/2022 5:05 PM, Kees Cook wrote: >> Enhance the details reported by "lsm=2Edebug" in several ways: > [=2E=2E=2E] > >Acked-by: Casey Schaufler Thanks! >I'm curious about what is driving this change=2E I was working on the ima stacking PoC and found the lsm=2Edebug output con= fusing to read, and I wrote it=2E :P So, I wanted to clarify things and mak= e sure stuff like lockdown was visible=2E Additionally, if we're going to k= eep the "lsm=3D" param as-is, I wanted it's value visible at boot so people= would know what to start from when making changes=2E -Kees --=20 Kees Cook