On Wed, Aug 03 2022 at 12:29P -0400, Daniil Lunev <dlunev@xxxxxxxxxxxx> wrote: > > This seems like an access control policy, which the Linux kernel already has a > > lot of mechanisms for. Chrome OS already uses SELinux. Couldn't this be solved > > by giving the device node an SELinux label that no one has permission to open? > That would be the ideal solution, but there is a number of challenges > that prevent > us enabling enforcement on all SELinux domains unfortunately. While in the long > run that would be a preferred option, in the short run this doesn't > seem feasible. I > would assume the problem of enabling full SELInux enforcement would plague > any big project that didn't have them enabled from the get going. > --Daniil I'm not going to take this patch. It isn't the proper way to handle preventing use of a DM device. In addition, the patch's header doesn't speak to a proper review/audit of implications this change would have on all aspects of a DM device's capabilities. If Chrome OS needs this as a stop-gap then please carry it as needed. Regards, Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
