FS#46006 - [linux] bluetooth SMP security bug

Attached to Project: Arch Linux
Opened by Ng Oon-Ee (ngoonee) - Tuesday, 18 August 2015, 00:56 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 October 2017, 14:13 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I have a bluetooth mouse (Lenovo N700) which was working before the recent kernel update. Now it connects (as shown on bluedevil) but does not respond. dmesg shows 'SMP security requested but not available'

Additional info:
* package version(s)
linux-4.1.6-1 from [testing]
* config and/or log files etc.
None relevant


Steps to reproduce:
Just connect the mouse. dmesg shows the below every 3 minutes or so while it is connected. Mouse works fine using the alternative USB dongle.

[ 181.637530] Bluetooth: SMP security requested but not available
[ 181.637543] Bluetooth: SMP security requested but not available
[ 181.637628] Bluetooth: SMP security requested but not available
[ 181.641022] NET: Registered protocol family 38
[ 373.949774] Bluetooth: SMP security requested but not available
[ 373.949787] Bluetooth: SMP security requested but not available
[ 373.949877] Bluetooth: SMP security requested but not available
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 15 October 2017, 14:13 GMT
Reason for closing:  No response
Comment by Ng Oon-Ee (ngoonee) - Tuesday, 18 August 2015, 00:59 GMT Comment by Ng Oon-Ee (ngoonee) - Friday, 04 September 2015, 01:46 GMT
Still an issue with 4.2. 4.1.5 was last working version. I am not receiving any replies on the linux-bluetooth mailing list on LKML.
Comment by Ng Oon-Ee (ngoonee) - Friday, 04 September 2015, 01:53 GMT
Due to above, I've added a bug to the kernel bugzilla - https://bugzilla.kernel.org/show_bug.cgi?id=104011
Comment by mattia (nTia89) - Monday, 02 October 2017, 20:18 GMT
is this issue still valid?

Loading...