From: dhowells@redhat.com (David Howells)
To: linux-security-module@vger.kernel.org
Subject: linux-next: UEFI Secure boot lockdown patchset
Date: Thu, 01 Mar 2018 11:06:55 +0000 [thread overview]
Message-ID: <26787.1519902415@warthog.procyon.org.uk> (raw)
Hi Stephen,
Can you pull the following branch into linux-next please? It does three
things:
(1) It restricts various accesses userspace may make upon the kernel when the
kernel is locked down.
(2) It engages the lockdown if UEFI Secure Boot mode is detected.
(3) It passes the UEFI Secure Boot mode indication across kexec.
The restrictions include:
- Enforcing the use of module signatures
- Enforcing the use of kexec image signatures
- Requring IMA to use secure boot rules
- Disabling:
- The kexec_load() syscall
- Use of /dev/{mem,kmem,port,kcore}
- Hibernation
- PCI BAR access
- Direct I/O port access
- Preventing direct port specification in drivers:
- SCSI EATA
- TIOCSSERIAL
- Module parameters
- Restricting:
- MSR access
- Certain ACPI features
- kprobes
- BPF
- Perf
- Debugfs
The aim of the restrictions is twofold:
(1) Prevent userspace from altering the kernel image directly (eg. by
/dev/mem) or indirectly (eg. by manipulating a device to do DMA);
(2) Prevent userspace from accessing crypto data stored in the kernel
(eg. filesystem keys).
A warning is logged if a restriction is triggered for which I've written a
manpage that is referenced in the message (see attached).
David
next reply other threads:[~2018-03-01 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 11:06 David Howells [this message]
2018-03-01 11:08 ` linux-next: UEFI Secure boot lockdown patchset Ard Biesheuvel
2018-03-01 11:24 ` David Howells
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=26787.1519902415@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-security-module@vger.kernel.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