Comment 4 for bug 1526836

It sounds like the content-hub portion can just be handled with changes to content-hub and the app doesn't need anything new.

OBEX file sending/receiving sounds like it doesn't need app policy at this time. That service can just run trusted (though it would be nice if it ran confined with a system profile since it will be handling untrusted input).

I need more details on RFCOMM/L2CAP and Low Energy-- how are apps supposed to use this? What would apparmor policy for apps look like? How do apps get access to the devices-- are they files in the filesystem? Are they virtual kernel devices? How do apps find out about them? How are they assigned? How can we integrate the trust-store for this sort of thing?