HIDD periphericals are disabled by default

Bug #59894 reported by Anthony Mercatante
6
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
Won't Fix
Wishlist
Bluetooth
Nominated for Feisty by Simon Ruggier

Bug Description

By default, connecting a HIDD peripherical requires to sudo hidd --connect "mac_address" at every boot since hidd is disabled in /etc/default/bluetooth file.

Changing HIDD_ENABLED from 0 to 1 makes connection far more easy since you just have to perform the sudo hidd --connect thing once and for all, and it'll work at reboot.

I think that the first manual connection avoids security issues.

There are dozens of messages on ubuntu boards complaining that hidd is hard to handle, so that could be a good way to make it easier I think.

Changed in bluez-utils:
importance: Untriaged → Wishlist
Revision history for this message
Onkar Shinde (onkarshinde) wrote :

This could go in edgy. It is just one line of change.

Changed in bluez-utils:
assignee: nobody → bluetooth
status: Unconfirmed → Confirmed
Revision history for this message
Anthony Mercatante (tonio) wrote :

The point is that this can be considered a security issue, even though that shouldn't cause any problem in my opinion, since the first connection of a peripherical (sudo hidd --connect _macaddress_) still has to be done once for the peripherical to be locally created.
The interest of activating this is that it avoids scripting or modifing /etc/default/bluetooth to make the reconnection at boot automatic.
Martin, any opinion concerning the security ?

Revision history for this message
Mario Limonciello (superm1) wrote :

As of hardy, the packages do have HID support enabled. It isn't using the traditional hidd binary, but rather the "Input service"

Changed in bluez-utils:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.