> The idea is that the signing process continues after boot and no code is run without first being checked.
How do you check system-wide libraries? They can be loaded at different time and so different addresses on two successive boots (depending on timing issues or randomized loaded), and they are lasy loaded (http://en.wikipedia.org/wiki/Lazy_loading) so they are constantly being modified - if those memory pages are loaded in memory at all.
Posted Jul 4, 2011 23:12 UTC (Mon) by brendan_wright (subscriber, #7376)
[Link]
> How do you check system-wide libraries?
You check the library loading code, and then the library code that is about to be loaded & relocated - if they haven't changed then the output can't have changed (except for addresses), so if they are "secure" then so should the output be.