From: "David Stockwell" <dstockwell@frequency-one.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Secure Simple Pairing (SSP)
Date: Fri, 20 Jun 2008 15:30:38 -0500 [thread overview]
Message-ID: <051401c8d314$821ca0a0$6701a8c0@freqonedev> (raw)
In-Reply-To: 1213981677.25820.57.camel@violet
WRT SSP: Fair enough...thanks.
In the meantime I will try to restrict the remote side to pairing using passkey/PIN.
DS
----- Original Message -----
From: "Marcel Holtmann" <marcel@holtmann.org>
To: "David Stockwell" <dstockwell@frequency-one.com>
Cc: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Sent: Friday, June 20, 2008 12:07 PM
Subject: Re: [Bluez-devel] Next Release, and Device.DiscoverServices
Hi David,
> Thanks for the feedback. Upgrading to 3.33 resolved the immediate problem with accessing UUIDs, and I do get the correct UUID
> from
> the remote (hurray!).
>
> FWIW, with SSP I intend to use only the "Just Works" model at this point, keeping the handshake as simple as possible (not a
> highly
> secure application). So, the capability parameter will be "NoInputOutput", if I am reading the code correctly (adapter.c).
> Hopefully, that will "JustWork", and I can proceed with the effort I originally undertook. At any rate, I will be watching CVS
> closely...
you will need some kernel patches to make SSP work. I am going to
publish them soon. Just finished the last testing of unlikely error and
corner cases.
Regards
Marcel
prev parent reply other threads:[~2008-06-20 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 14:47 [Bluez-devel] Next Release, and Device.DiscoverServices David Stockwell
2008-06-18 15:04 ` Marcel Holtmann
2008-06-20 16:55 ` David Stockwell
2008-06-20 17:07 ` Marcel Holtmann
2008-06-20 20:30 ` David Stockwell [this message]
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='051401c8d314$821ca0a0$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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