From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: devel@edk2.groups.io, osy@turing.llc,
Ard Biesheuvel <ardb@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>,
dann frazier <dann.frazier@canonical.com>
Subject: Re: [edk2-devel] ArmVirtPkg: non-executable EFI_LOADER_DATA breaks GRUB on Ubuntu 22.04
Date: Mon, 17 Jul 2023 11:30:56 +0200 [thread overview]
Message-ID: <3dmys7b2ml4z2p2z5ucacq66d2q5ynrlpycmdg7rf2ks5zpgv3@hr45oxed2mmh> (raw)
In-Reply-To: <CAKbZUD2xCD03Pf8erBA86WL=7nz2CvBnoBLmonN1n52G1m12Sg@mail.gmail.com>
Hi,
> > The idea is: Improve page fault handler to (a) print a big'n'fat
> > warning, and (b) loosening up memory permissions for the faulting
> > page address.
> >
> > No patch for that emerged (yet?).
>
> Ack. I can work on that.
FYI: There was a patch series on the list last week to move various
paging / security related options from compile time (PCD) to runtime
(config struct in HOB). All NX settings are in there, also page guard
and heap guard. Also some (very basic) support for config profiles.
With that in place it would be possible to make this configurable in
uefi firmware settings (or via fw_cfg, or both).
> Also, what's the situation on this for x86? I assume it's a lot worse there?
Currently x86 is less problematic in practice, but only because many of
the security features are not (yet) enabled.
Note it's not only grub+shim, the linux kernel stub is affected too.
The new, uefi-stub-only archs (armv7, armv8,riscv) are fixed meanwhile,
and they all use the common zboot code. x86 is wip still, ard has a
patch series in flight, it's more tricky there due to hybrid bios/uefi
kernels and other legacy cruft ...
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#106960): https://edk2.groups.io/g/devel/message/106960
Mute This Topic: https://groups.io/mt/100057351/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-07-17 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 21:16 ArmVirtPkg: non-executable EFI_LOADER_DATA breaks GRUB on Ubuntu 22.04 osy
2023-07-10 15:58 ` [edk2-devel] " Pedro Falcato
2023-07-10 17:09 ` osy
2023-07-11 6:58 ` Gerd Hoffmann
2023-07-13 16:57 ` Pedro Falcato
2023-07-13 17:20 ` Ard Biesheuvel
2023-07-13 17:41 ` Pedro Falcato
2023-07-13 18:22 ` Oliver Smith-Denny
2023-07-13 23:03 ` Michael D Kinney
2023-07-17 9:30 ` Gerd Hoffmann [this message]
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-list 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=3dmys7b2ml4z2p2z5ucacq66d2q5ynrlpycmdg7rf2ks5zpgv3@hr45oxed2mmh \
--to=devel@edk2.groups.io \
/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