On Dec 1, 2014 6:57 AM, "Stephen Smalley" <[email protected]> wrote: > > Suggests that you have a service without its own domain and therefore > left in the init domain. Do you have the dumpstate domain and is its > executable labeled correctly?
You know what I only checked persistent service domains, let me check this. Thanks. > > On Sun, Nov 30, 2014 at 6:40 PM, William Roberts > <[email protected]> wrote: > > I am working on a device and this popped up during CTS run: > > > > type=1400 msg=audit(1417375511.150:389): avc: denied { read write } for > > pid=3946 comm="dumpsys" path="socket:[5849]" dev=sockfs ino=5849 > > scontext=u:r:drmserver:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket > > > > Not really sure where this socket came from, is it an anonymous socket > > passed down from init to all children for them to write their dumpsys > > information too? Should I just do a dynamic type transition to > > dumpsys_socket? > > > > Did this ever pop up on mainline dev? I don't see anything in base master > > sepolicy. > > > > -- > > Respectfully, > > > > William C Roberts > > > > > > _______________________________________________ > > Seandroid-list mailing list > > [email protected] > > To unsubscribe, send email to [email protected]. > > To get help, send an email containing "help" to > > [email protected].
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
