** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Add Bluetooth apparmor policy
To manage
** Tags added: bluetooth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Add Bluetooth apparmor policy
To manage notifications about this bug go to:
@Michael: Does this mean after OTA-11 you can publich your Bluetooth app
to the official Ubuntu Store? :) Or we will still need to use wich is
published in the OpenStore?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apparmor-easyprof-ubuntu (16.04.6) xenial; urgency=medium
* add reserved ubuntu/bluetooth (LP: #1569582)
-- Jamie Strandboge Tue, 10 May 2016 17:02:27 -0500
apparmor-easyprof-ubuntu (1.3.17) vivid; urgency=medium
* add reserved ubuntu/bluetooth (LP: #1569582)
--
FYI, this is ready for QA signoff: https://requests.ci-
train.ubuntu.com/#/ticket/1404
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Add Bluetooth apparmor policy
To manage
To test these clicks, we either need new clicks that specify the
'bluetooth' reserved policy or, modify /var/lib/apparmor/clicks/...json
to add "bluetooth" to the policy_groups, then rm -f
/var/lib/apparmor/profiles/click_..., then do 'sudo aa-clickhook' (this
modifies the installed security
This bug was fixed in the package apparmor-easyprof-ubuntu - 16.10.1
---
apparmor-easyprof-ubuntu (16.10.1) yakkety; urgency=medium
* add 16.10 policy
* add bluetooth-net and bluetooth-file-transfer to pending/
* add reserved ubuntu/bluetooth (LP: #1569582)
-- Jamie
FYI, vivid packages are here: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-015
I'm still turning the crank on xenial and the landings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I examined all the policy and created a very broad profile called
"bluetooth": http://bazaar.launchpad.net/~ubuntu-security/apparmor-
easyprof-ubuntu/trunk/view/head:/data/policygroups/ubuntu/1.3/bluetooth
This gives all access to bluez and is therefore reserved. I was able to
successfully
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Add Bluetooth apparmor policy
To manage
FYI, I'm working through the policy in a very fine-grained manner to
understand it and will post my results here. I can say that the first
click example seems to work ok on the sender, but all transfers fails--
either to my laptop (even after enabling bluetooth and visibility and
using
FYI, we decided on IRC that we would add a single reserved policy group
for now, named 'bluetooth'. This will allow full access to bluez. This
will be reserved in the first iteration because there are information
leaks and the device can be placed into discovery mode. Other accesses
were not
Note, I have not played with Low Energies profiles yet. So that needs to
be added too but I don't have any LE devices handy right now. Will add
more details when I get there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching another click that can establish a bluetooth connection
between 2 devices. One side creates an SPP chat server, the other can
connect to it as a client.
This can be used to exercise:
On the server side,
* the local Bluetooth device is made visible so that the client can scan for it
*
Ok, the attached .click should work on all our supported devices. You do
need rc-proposed in order for receiving files to work. Sending files via
content hub should work on stable too (assuming apparmor policies are in
place).
--
You received this bug notification because you are a member of
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Add Bluetooth apparmor policy
To manage
Is there a click I can use to play with this? Will it work on mako? Do I
need rc-proposed, silos, etc?
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Package changed: apparmor
Oh, some more info:
For the device discovery, it uses the "BluetoothDeviceDiscoveryModel"
[1], for sending the file it uses QBluetoothTransferManager [2], both
from the Qt API
[1] http://doc.qt.io/qt-5/qml-qtbluetooth-bluetoothdiscoverymodel.html
[2]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569582
Title:
Oh, some more info:
For the device discovery, it uses the "BluetoothDeviceDiscoveryModel"
[1], for sending the file it uses QBluetoothTransferManager [2], both
from the Qt API
[1] http://doc.qt.io/qt-5/qml-qtbluetooth-bluetoothdiscoverymodel.html
[2]
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
21 matches
Mail list logo