On 02/17/2014 06:59 PM, Tai Nguyen (tainguye) wrote:
> Our device uses blueZ stack instead of bluedroid, and we have audit message
> about unlabeled socket
>
>
> audit(1392652331.875:225): avc: denied { read } for pid=5249
> comm="bluetoothd" scontext=u:r:bluetoothd:s0 tcontext=u:object_r:unlabeled:s0
> tclass=socket
>
> This could be the hci socket that blueZ uses. How do I set security label for
> this type of socket?
The fact that it is unlabeled suggests that you have a kernel bug.
Kernel version?
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to
[email protected].
