settings: Add doc for the connecting devices hashtable
settings: Better support for remote-initiated pairing

When the pairing is remote initiated, show a dialogue that'll
only ask to enter the same PIN as on the remote device, and
dismiss the dialogue straight away.
settings: Pass "self" to properties_for_device()
settings: Fix debug output in pin.c

Again!
settings: Add work-around for BlueZ "type" bug

See http://thread.gmane.org/gmane.linux.bluez.kernel/41471
lib: Add test case for pin code generation
settings: Implement authorise service for HID devices

If they're paired or trusted, allow the remote device to connect.
This can happen if we didn't know that the remote device actually
did input (like, if it got removed after the reverse SDP), so
hack around that.
settings: Don't override "confirm_pin"

When we detect a PIN code by name, we don't need to confirm the
PIN code, so leave confirm_pin alone.

Also make sure that the display_pin is set to show the user.
settings: Simply bail out when the name isn't known

If we get a pairing request and we don't even have a name for
the device, just bail.
settings: Fix for remote pairing with known devices

For devices where we know the PIN for certain, and when the
pairing is remote initiated, make sure that we don't show any
dialogues.
settings: Fix memory leak in pincode_callback

Garbage collection FTW.
settings: Fix pairing of the PS3 BD remote

Straight after discovery, the legacy pairing might not have
been detected yet, so go with the information we have to
detect whether we need to not use pairing.

Fixes an assertion trying to pair the PS3 BD remote.
settings: Re-add special device special-cases

The autopair plugin isn't used for remote-initiated pairings,
like a mouse trying to reconnect to the device it connected
to before.
settings: Fix pairing pre-Bluetooth 2.1 keyboards

Rejecting the bluetoothd generated PINs doesn't actually work.
We need to actually display the code coming from bluetoothd,
so it can be entered on the keyboard.