Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5518180pxj; Wed, 26 May 2021 12:26:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyPbatQhX0AuoxgNSTyDeUdx7irf6f4r5EUbGjFzSBJp9qC0D3aMRq+x3zBRfEsVHWgzlmd X-Received: by 2002:a17:906:4c54:: with SMTP id d20mr35981832ejw.513.1622057192757; Wed, 26 May 2021 12:26:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622057192; cv=none; d=google.com; s=arc-20160816; b=caxG0GEMSnSPYr7XDfbO6DuGYylBoEteZDq+5iCwlBQnhU9T8qIS8d9sb1Zf4m5nS3 OdhM0E/bpFHfFZDZfVQDl23WVJGjl/VGxATm2jDq6iHNE86TKJiwffPZ5S3vydbWR9uE PZwRsuDCJfCwtrKhOpxumdANp4EcfDXou3Jyhftti24wSlNi8w4Hzcf8+DTZ1nqaZyaN OchgxsxrDqO+myqKC++b088OJQkINjIRHGGNIQziRpl9PDDZUsqkx52T/cio8ciEVV7V nwyefojlkmPZ46DyEsMwYNdh6MP6/xDZqWhri9RXnr3kWqiYZPbNbHGO+b1MfaTnfjbk ISOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=w1BBOqU67n/OOIRVX2OOnVm03dC+SploPCeZsi2hwhQ=; b=W6plD2O+R3YfzkLbqG4tIDXxyi4S8GgvzJqVyxqm4bED5i24u/v9ob1cwp3tLZ5UUT 2DS7k0P4OsCEEjGNi2Cyc1FDaeAf7cLP8XS+bnVmJCehctMrkB0xDfIc+waP+4kcMlcm 9JyCR/ktQRRqPQ6NArnk94k42Z/NcgutYP01u6MYvsgLG5VkUUHlvnGRA8PwbL3fdY/m sJPdj/iwcBoGDvkTOJyEjP0MMNsfrhRYdCtHigqSwg1jK2SXB4Ni5rH/AzwZg27lVlLC f4IeiYQABaFSaFvlTPrxAWGJochEsQcHByLa1oyOVVnvNioLrXtX+ORnLJWfkqisKE23 ob2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k20si187134edv.443.2021.05.26.12.26.08; Wed, 26 May 2021 12:26:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234420AbhEZRgh (ORCPT + 99 others); Wed, 26 May 2021 13:36:37 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:37125 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231461AbhEZRgh (ORCPT ); Wed, 26 May 2021 13:36:37 -0400 Received: from 2.general.dannf.us.vpn ([10.172.65.1] helo=localhost) by youngberry.canonical.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1llxQt-0004cM-UZ; Wed, 26 May 2021 17:35:04 +0000 From: dann frazier To: linux-man@vger.kernel.org, Michael Kerrisk , David Howells , Heinrich Schuchardt Cc: linux-kernel@vger.kernel.org, Pedro Principeza Subject: [PATCH] kernel_lockdown.7: Remove description of lifting via SysRq (not upstream) Date: Wed, 26 May 2021 11:34:55 -0600 Message-Id: <20210526173455.971103-1-dann.frazier@canonical.com> X-Mailer: git-send-email 2.31.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The patch that implemented lockdown lifting via SysRq ended up getting dropped[*] before the feature was merged upstream. Having the feature documented but unsupported has caused some confusion for our users. [*] http://archive.lwn.net:8080/linux-kernel/CACdnJuuxAM06TcnczOA6NwxhnmQUeqqm3Ma8btukZpuCS+dOqg@mail.gmail.com/ Signed-off-by: dann frazier --- man7/kernel_lockdown.7 | 6 ------ 1 file changed, 6 deletions(-) diff --git a/man7/kernel_lockdown.7 b/man7/kernel_lockdown.7 index 30863de62..29ffd55c3 100644 --- a/man7/kernel_lockdown.7 +++ b/man7/kernel_lockdown.7 @@ -33,12 +33,6 @@ where X indicates the process name and Y indicates what is restricted. .PP On an EFI-enabled x86 or arm64 machine, lockdown will be automatically enabled if the system boots in EFI Secure Boot mode. -.PP -If the kernel is appropriately configured, lockdown may be lifted by typing -the appropriate sequence on a directly attached physical keyboard. -For x86 machines, this is -.IR SysRq+x . -.\" .SS Coverage When lockdown is in effect, a number of features are disabled or have their use restricted. -- 2.31.1