Hi Tushar, On Sun, 2020-11-01 at 14:26 -0800, Tushar Sugandhi wrote: > Currently, IMA does not restrict random data sources from measuring > their data using ima_measure_critical_data(). Any kernel data source can > call the function, and it's data will get measured as long as the input > event_data_source is part of the IMA policy - CRITICAL_DATA+data_sources. > > To ensure that only data from supported sources are measured, the kernel > subsystem name needs to be added to a compile-time list of supported > sources (an "allowed list of components"). IMA then validates the input > parameter - "event_data_source" passed to ima_measure_critical_data() > against this allowed list at run-time. > > This compile-time list must be updated when kernel subsystems are > updated to measure their data using IMA. > > Provide an infrastructure for kernel data sources to be added to > IMA's supported data sources list at compile-time. Update > ima_measure_critical_data() to validate, at run-time, that the data > source is supported before measuring the data coming from that source. For those interested in limiting which critical data to measure, the "data sources" IMA policy rule option already does that. Why is this needed? thanks, Mimi -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
