From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1384864264.2027.22.camel@nuvo> Subject: autopair corner cases From: Bastien Nocera To: linux-bluetooth@vger.kernel.org Date: Tue, 19 Nov 2013 13:31:04 +0100 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Heya, There's a bunch of corner cases that the autopair plugin doesn't handle and that we used to handle in gnome-bluetooth with BlueZ 4.x. 1) First is the case of the PS3 BD Remote that will reject authentication when you try to pair to it. gnome-bluetooth knows not to pair with it. > > > > Is there a way to say "we can't actually pair" when the client requested pairing already? Or is that considered a security problem? 2) The second case is pairing this "funny" keyboard that's the iCade controller. In gnome-bluetooth, we had special code to generate only joystick movements for the pairing, rather than hard to determine buttons, so we'd end up with a 6-digit pin using only 1 through 4. > > 3) We have a whole list of GPS that don't use present themselves as anything special apart from the name. Most use "0000", but some use things like "NAVMAN" or "12345678" > > > > > 4) Audio devices will mostly already be supported by the autopair code (yay!), though we have a few stragglers, most notably this speaker that can use random pincode, as long as they're only 4 digits in length: > > 5) Printers are missing from the list, that should be an easy fix. I'll try and send patches for cases 2 through 4, using a static table in the autopair plugin. If that's not acceptable, I'll create a new higher-priority plugin that handles those corner cases. Cheers