Kees Cook e0e4ed404b vbutil_kernel: copy zeropage fully ...

When copying the vmlinuz zeropage, the entries were being truncated even
though the boot protocol version was being retained. This means that
booting a kernel that depended on details from the zeropage's ignored
areas would find invalid information. Fix this by copying out the entire
possible range of memory.

BUG=chromium:230212
TEST=kernels can boot with CONFIG_RELOCATABLE
BRANCH=None

Change-Id: Ifb94bedcf881e17ab20fff44d8c1c1885b15ef9e
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/47832
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Bill Richardson <wfrichar@chromium.org>

2013-04-11 11:29:39 -07:00

..

bmpblk_util.h

Enable EFIv1 compression in bmpbklk_utility.

2011-02-14 10:28:03 -08:00

bmpblk_utility.h

bmpblock v1.2 - render HWID inside vboot_reference

2011-08-24 09:27:12 -07:00

eficompress.h

Enable EFIv1 compression in bmpbklk_utility.

2011-02-14 10:28:03 -08:00

gbb_utility.h

gbb_utility: add --flags parameter.

2011-08-29 16:22:09 -07:00

image_types.h

bmpblock v1.2 - render HWID inside vboot_reference

2011-08-24 09:27:12 -07:00

kernel_blob.h

vbutil_kernel: copy zeropage fully

2013-04-11 11:29:39 -07:00

tpmextras.h

TBR: reviewed in person with semenzato

2010-09-02 11:37:51 -07:00

verify_data.h

VBoot Reference: Refactoring Part 3

2010-03-31 13:26:55 -07:00