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?
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1526836
Title:
Add qml-module-qtbluetooth support
Status in Canonical System Image:
Confirmed
Status in apparmor package in Ubuntu:
Incomplete
Status in ubuntu-touch-meta package in Ubuntu:
Fix Committed
Status in ubuntu-touch-meta package in Ubuntu RTM:
Fix Released
Bug description:
Add to the seed
Make available in the ota9 framework
Add apparmor policy
API reference at http://doc.qt.io/qt-5/qtbluetooth-index.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526836/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
