> 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 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
