[Bug 644198] Re: Ubuntu LIve Cd does not enable bluetooth before choice menu in live-cd

[Stéphane Graber]

Right so just spent some time thinking about it :)
We basically have three possible ways of "fixing" this bug (though not all fix the overall problem):
 1) Disable /lib/udev/rules.d/97-bluetooth-hid2hci.rules which will make some (not all by far) USB bluetooth receiver appear as USB HID devices hiding the bluetooth stack entirely.
 2) Run bluetooth-applet from ubiquity-dm
 3) Write our own agent dealing with the connections and our install time policy

The problem with 1) is that it'd only work with a limited set of USB
receivers and will only work during install, not post-install so just
delaying the problem to the first boot.

The problem with 2) is that it'll still prompt the user for the pin code
or confirmation which they'll have no way to do as they won't have any
input device at that point.

So I started working on 3) with the following plan:
 - Spawn a small bluetooth agent that I wrote (based on bluez-simple-agen): http://paste.ubuntu.com/875275/
 - This agent will spawn and for 5 minutes will accept any HID device connecting, also adding it to bluez's trust list.
 - The filtering is done using a mask of 0x500 (found using http://bluetooth-pentest.narod.ru/software/bluetooth_class_of_device-service_generator.html)
 - After these 5 minutes, it'll spawn bluetooth-daemon which will deal with any bluetooth device connecting from this point.
 - Post-install, ubiquity will copy /var/lib/bluetooth/ to the target so that the trust is there at boot time and the input devices work as expected.


The problem with this solution is on the security side obviously as any HID bluetooth device connecting during these 5 minutes will automatically be allowed to connect at any time on the install system. I think that the 5 minutes limitation and the bitmask mitigate that enough to be acceptable (not that we have another solution really ...).

I'm subscribing the security team for review and approval, in the mean
time I'll at least add bluetooth-applet and /var/lib/bluetooth/ to
ubiquity. The switch to my custom agent would be done by overriding
/usr/bin/bluetooth-applet through casper.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/644198

Title:
  Ubuntu LIve Cd does not enable bluetooth before choice menu in live-cd

Status in “ubiquity” package in Ubuntu:
  Triaged
Status in “ubiquity” source package in Oneiric:
  Won't Fix
Status in “ubiquity” source package in Precise:
  Triaged

Bug description:
  My Intel Duo Core Multi-Boot Apple Macintosh doe not work right with the latest Ubuntu Beta 10.10 Maverick Meerkat Live -C.D.'s.
  The Live C.D. loads to the Language/Try Ubuntu or Install Ubuntu, but does not get past that point because I have a wireless Bluetooth mouse and a wireless Bluetooth Keyboard. If I plug in a usb keyboard i can tab to try ubuntu and it will load up to bluetooth load and asks for a pairkey for my wireless mouse, i don't think i have one, or don't know it. this is a new bug or obstacle, i have been able to use multiple other Live cd's without this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: casper (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Tue Sep 21 01:30:54 2010
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: casper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/644198/+subscriptions