Currently, vboot1 and vboot2 both have library functions to verify the vboot1 data structures. The vboot2 versions are more efficient and require fewer external APIs.
Port the vboot1 higher-level functions to use the vboot2 library, then remove the duplicate vboot1 code.
This is part of a longer process of refactoring the vboot1 kernel verification code so that the UI loop can move out to depthcharge (where it's easier to support non-clamshell devices) instead of being buried inside vboot_reference.
Comment 1 by rspangler@chromium.org
, May 25 2016