[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Linux DRTM on UEFI platforms
From: |
Matthew Garrett |
Subject: |
Re: Linux DRTM on UEFI platforms |
Date: |
Wed, 30 Mar 2022 08:27:55 +0100 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Wed, Mar 30, 2022 at 09:23:17AM +0200, Ard Biesheuvel wrote:
> On Wed, 30 Mar 2022 at 09:19, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > From a conceptual perspective we've thought of the EFI stub as being
> > logically part of the bootloader rather than the early kernel, and the
> > bootloader is a point where the line is drawn. My guy feeling is that
> > jumping into the secure kernel environment before EBS has been called is
> > likely to end badly.
>
> If you jump back into the system firmware, sure.
>
> But the point I was trying to make is that you can replace that with
> your own minimal implementation of EFI that just exposes a memory map
> and some protocols and nothing else, and then the secure launch kernel
> would be entirely in charge of the execution environment.
We can't just replace system firmware with an imitation of the same -
for instance, configuring the cold boot prevention memory overwrite
requires us to pass a variable through to the real firmware, and that's
something that we do in the stub.
- Linux DRTM on UEFI platforms, Matthew Garrett, 2022/03/29
- Re: Linux DRTM on UEFI platforms, Ard Biesheuvel, 2022/03/30
- Re: Linux DRTM on UEFI platforms, Matthew Garrett, 2022/03/30
- Re: Linux DRTM on UEFI platforms, Ard Biesheuvel, 2022/03/30
- Re: Linux DRTM on UEFI platforms, Matthew Garrett, 2022/03/30
- Re: Linux DRTM on UEFI platforms, Ard Biesheuvel, 2022/03/30
- Re: Linux DRTM on UEFI platforms,
Matthew Garrett <=
- Re: Linux DRTM on UEFI platforms, Ard Biesheuvel, 2022/03/30
- Re: Linux DRTM on UEFI platforms, James Bottomley, 2022/03/30
Re: Linux DRTM on UEFI platforms, Daniel P. Smith, 2022/03/30