Make the root cause of system_u and object_r nonexistence clearer
Closed this issue · 1 comments
dburgener commented
Users are sometimes confused when they get a large number of errors about system_u and object_r not being defined in policy when running selint. SELint is told to assume the existence of these by the config file (assume_users and assume_roles config options), and so when the default config is loaded, this should go away. Unfortunately, this can cause confusion for users who choose to run selint without installing it and don't specify a config on the command line.
We should come up with some default behavior that either causes this issue to not occur, or makes it clear to the user why it's occurring and how to address it.