A security analyst is validating the Mac policy on a setof android devices. The policy was written to ensure non-criticalapplications are unable to access certain resources. When reviewingdmesg, Dallas notes many inches is such as:
Avc: defined { open } for pid=1018 comm=â€ircâ€path=â€/dev/if0†dev=â€tmpfs†scontext=u:r:irc:sc:s0tcontext=u:objective_r:default:s0tclass=chr_filepermissive=1
Despite the deny message, this action was stillpermitted. Which of the following is the most likely fix for thisissue?
add the objects of concern to defaultcontext
set the devices to enforcing mode
create separate domain and context file
Rebuild the sepolicy, reinstall, and test
