From: "Michael Adler" <michael.adler@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Michael Adler <michael.adler@siemens.com>
Subject: [cip-dev] [PATCH 0/1] [isar-cip-core] Secureboot: disable initramfs debug shell
Date: Fri, 19 Mar 2021 08:20:35 +0100 [thread overview]
Message-ID: <20210319072036.16091-1-michael.adler@siemens.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi everyone,
the following patch intends to close a loophole in the secureboot boot chain.
By default, Debian Buster's initramfs drops the user to an interactive debug
shell in case of a severe error (e.g. rootfs cannot be mounted). This is
essentially a root shell and can be abused to tamper with the system.
This feature can be disabled by appending panic=0 to the kernel cmdline.
Kind regards,
Michael
Michael Adler (1):
Secureboot: Disable initramfs debug shell
wic/qemu-amd64-efibootguard-secureboot.wks | 2 ++
wic/qemu-amd64-efibootguard.wks | 2 ++
wic/simatic-ipc227e-efibootguard.wks | 2 ++
wic/swupdate-partition.inc | 2 --
4 files changed, 6 insertions(+), 2 deletions(-)
--
2.31.0
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6298): https://lists.cip-project.org/g/cip-dev/message/6298
Mute This Topic: https://lists.cip-project.org/mt/81450089/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-03-19 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 7:20 Michael Adler [this message]
2021-03-19 7:20 ` [cip-dev] [PATCH 1/1] Secureboot: Disable initramfs debug shell Michael Adler
2021-03-19 8:57 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210319072036.16091-1-michael.adler@siemens.com \
--to=michael.adler@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).