Message-ID: <0a3901c8e03c$0fd66eb0$6701a8c0@freqonedev>
From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Date: Mon, 7 Jul 2008 09:16:32 -0500
MIME-Version: 1.0
Subject: [Bluez-devel] SSP testing and BlueZ
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

While attempting to test SSP with 3.34-3.35, I found that I was unable 
to pair with SSP; I was able to pair with the legacy 
pin-request/response mode.  I checked the HCI level of my aging BT 
dongle (somehow this sounds a bit "dirty"), and found that it was only 
HCI 1.1 compliant.  Replacing it with a BT2.0+EDR compliant dongle, I 
found that it still would not pair with SSP.

Consulting with CSR, they confirmed that unless both devices are 
Bluetooth HCI 2.1 compliant, SSP will not work; it will always fall back 
to Legacy pairing.

I searched yesterday for HCI 2.1-compliant dongles, and found only one, 
from Logitec (not Logitech) in Japan.  These are not available in the US 
market.

So much for SSP testing, for me at least.  Fortunately for me, my app 
does not need this enhanced security...

David Stockwell
Frequency One 


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel