From: Marcel Holtmann <marcel@holtmann.org>
To: David Stockwell <dstockwell@frequency-one.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Next Release, and Device.DiscoverServices
Date: Fri, 20 Jun 2008 19:07:57 +0200 [thread overview]
Message-ID: <1213981677.25820.57.camel@violet> (raw)
In-Reply-To: <04fa01c8d2f6$65597b50$6701a8c0@freqonedev>
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
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-06-20 17:07 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 [this message]
2008-06-20 20:30 ` Secure Simple Pairing (SSP) 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=1213981677.25820.57.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dstockwell@frequency-one.com \
/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