Daniel J Walsh wrote:
If we can not duplicate this functionality then I NAK the change
from booleans to tunables.
You could actually force a downgrade to a pre-tunable format and
use that policy to do the setroubleshoot lookups. Since the policy
is already linked/expanded and just needs to be written out twice
it wouldn't add much time to policy building (granted that adding
_any_ time to policy building is adding too much...)
I might not have explained it correctly, I really meant the policy
would have to toggle each tunable/boolean at a time and see if the AVC
was allowed. Recompiling the policy for each tunable/boolean change
would be not be supportable for Time and CPU reasons.
What I mean is, if you set the policy writer to not use tunables (by whatever
method that is) it'll write them out as regular booleans and setroubleshoot
could load that policy (which should be the same as the loaded one, except with
extra rules and booleans), toggle the booleans like it does now and do access
vector lookups to see if a boolean would enable one. Same method as now, there
would just be 2 policies on disk. Call the one with everything the "debug" policy :)
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
