Fix setting paired state when device->authr is false
Some buggy controllers might generate a link key notification even after
a disconnect has been requested. To make sure that device->paired is in
sync with the real paired state set the value independent of
device->authr when a link key notification happens. Below is a snippet
of such buggy (or at least strange) behavior from a controller:
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 6 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Link Key Notification (0x18) plen 23
bdaddr 00:26:CC:77:xx:xx key 33E6F2B75FC870AA794BB6249EBD6AC6 type 0
Type: Combination Key
> HCI Event: Auth Complete (0x06) plen 3
status 0x00 handle 6
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 6 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 6 reason 0x16
Reason: Connection Terminated by Local Host
2 files changed
