From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] SSP testing and BlueZ
Date: Mon, 7 Jul 2008 09:16:32 -0500 [thread overview]
Message-ID: <0a3901c8e03c$0fd66eb0$6701a8c0@freqonedev> (raw)
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
next reply other threads:[~2008-07-07 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 14:16 David Stockwell [this message]
2008-07-11 20:17 ` [Bluez-devel] SSP testing and BlueZ Martin Karger
2008-07-11 20:56 ` David Stockwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0a3901c8e03c$0fd66eb0$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox