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 X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A551FC4360F for ; Thu, 7 Mar 2019 00:12:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 667D520675 for ; Thu, 7 Mar 2019 00:12:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="ljG3pXDv" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726227AbfCGAMc (ORCPT ); Wed, 6 Mar 2019 19:12:32 -0500 Received: from mail-it1-f196.google.com ([209.85.166.196]:35093 "EHLO mail-it1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726121AbfCGAMb (ORCPT ); Wed, 6 Mar 2019 19:12:31 -0500 Received: by mail-it1-f196.google.com with SMTP id 188so13115003itb.0 for ; Wed, 06 Mar 2019 16:12:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ezOAVi/+85xQ0cQ5uMUhyfKczC6Zcgc3Xf7/a9KMpt0=; b=ljG3pXDvh/JGlXb3cfYGf7sz7TnKMIjIB2DmSLlmU4D2ZQAv8s7NDzdS4aQBZGn86v mCgxEM9mHOTEdQdE/50dDMpay9ORCxGyAK2BysihUw4ExkoZ3p7gP9WgIVNSeau8yxal gkMfi9530MJUOaAFOjZYghkIFxSptRTN5A+bVA893Jt3QXt3WYZh2nBZCs/9NDpVVmS9 vOU/GNvfMQC+iAaUB6UByNG/g91jxSIFx8JU0gkiT8DPDcjAOpCuJRd45k/h6cMatOAg fs4YQFp9ZOewTRxHvKVRtMIRe4LhaFf2XPaCSkU77PhKM6vB26g7SxgUrOjvYWJ6U1fW 2YVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ezOAVi/+85xQ0cQ5uMUhyfKczC6Zcgc3Xf7/a9KMpt0=; b=oJZqEVdcicnU9SGYM0hinm7OG6mNZB7zRETipuLCw/MFYh8GSaoNrI4IsJ92elWv5L 8UFMK5tcDC3FBIRmj0ifOve/ZQCg20sGfIQsVY2W3i4cnaGfzBxXcrF+oNzRlzFkEqdz 2ICjFrfrmgK3v7A6r5ghB3dMT1G58Up7n2/SAkUWBajx350vHqDP7H85+9qu36EnoqQp 1BxY3QRkFHr5eMR9qri6WfBdX4H1sbrMwZyYDFw8KBT9mLLaCjee8v11ph+zx+yN2hja nx3lbC2oZz4tEGqQcIVWNBiRXnESt19JuaBOUcZ/YtUth45VjIgSFecwUYhsJp9IyabX Wbbg== X-Gm-Message-State: APjAAAXkAMcIZhiN/387LH2qStfT4jn4xrsimbzYryEn32BBDhsvMFJi 8zimpa1Bi1g3PjpPgW9ZulLMbYZxQD1HnYls8M6ebA== X-Google-Smtp-Source: APXvYqx+7BfFRYc9FIjPhKRtXKZBgJQQsl/EUB+DtnJOMAbPmXfyRM1JLwSZZfHZsIewZi7pN1cOctBHJ5j5QRGtF8s= X-Received: by 2002:a24:2c48:: with SMTP id i69mr3942607iti.161.1551917550566; Wed, 06 Mar 2019 16:12:30 -0800 (PST) MIME-Version: 1.0 References: <20190306235913.6631-1-matthewgarrett@google.com> <20190306235913.6631-3-matthewgarrett@google.com> <7bcd6149-332d-15f8-31e1-ef0a6b7f496e@infradead.org> In-Reply-To: <7bcd6149-332d-15f8-31e1-ef0a6b7f496e@infradead.org> From: Matthew Garrett Date: Wed, 6 Mar 2019 16:12:19 -0800 Message-ID: Subject: Re: [PATCH 02/27] Add a SysRq option to lift kernel lockdown To: Randy Dunlap Cc: jmorris@namei.org, LSM List , Linux Kernel Mailing List , David Howells Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 6, 2019 at 4:10 PM Randy Dunlap wrote: > > On 3/6/19 3:58 PM, Matthew Garrett wrote: > > From: Kyle McMartin > > > > Make an option to provide a sysrq key that will lift the kernel lockdown, > > thereby allowing the running kernel image to be accessed and modified. > > You still need to document this in Documentation/admin-guide/sysrq.rst, > like I mentioned last week. Hm.. On reflection this patch doesn't make much sense without the automatic lockdown enable functionality, so I'll just drop it from the patchset instead. Thanks!