From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: False negative checking for SSP support From: Marcel Holtmann To: Johan Hedberg Cc: Bastien Nocera , BlueZ development In-Reply-To: <20090613194310.GA27600@jh-x301> References: <1244919968.11069.4360.camel@localhost.localdomain> <20090613194310.GA27600@jh-x301> Content-Type: text/plain Date: Sat, 13 Jun 2009 21:47:41 +0200 Message-Id: <1244922461.1852.5.camel@violet> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Johan, > > I'm slowly adding SSP 2.1 support to gnome-bluetooth. For that, I got a > > laptop running Fedora 11, with a Bluetooth 2.1 dongle, in addition to > > the one in the machine I'm trying to pair from. > > > > Is there any reason why the other machine shows up as not supporting > > SSP, when it actually does? > > Do both of the machines support 2.1? The LegacyPairing property tells you > whether SSP is likely to be triggered or not when you try to pair. It > doesn't tell you whether other device supports SSP or not e.g. if your > local adapter is pre-2.1 (but if your local adapter is 2.1 capable the > property should be a good indicator of SSP support). > > In theory it is possible to get a false positive for LegacyPairing if the > other device is 2.1 but for some reason has extended inquiry response > disabled (iirc the spec mandates EIR if SSP is enabled). However, if both > sides have bluez and 2.1 HW then both EIR and SSP should automatically be > get enabled by bluetoothd. If that's not happening we may have a bug > somewhere (which I haven't seen with any of my 2.1 adapters). it is actually the other way around. You can only use EIR if you enable SSP. However you can have SSP without EIR. Regards Marcel