From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Connecting to a two-way headset
Date: Tue, 19 Feb 2008 21:26:30 +0100 [thread overview]
Message-ID: <47BB3B76.6000302@suse.de> (raw)
In-Reply-To: <47B96FE9.90900@wurmsdobler.org>
Peter Wurmsdobler schrieb:
> Hello,
> =
> >> I was prompted by a graphical (rather than command-line) prompt
> >> (seemingly from the applet) saying "Pairing request for device:
> >> HBH-PV702 (00:1C:A4:20:CE:BE) Enter passkey for authentication:"
> How is this "BlueTooth Applet" actually triggered such that it prompts =
> the user? What does it do (what code should I look in to understand)? =
> How would I replace what the Applet does by something else in an =
> embedded application, i.e. without gnome and kde?
I'll try to provide a little piece of the big picture here. Beware: i am not
an expert on the matter and it might not be totally accurate, but it should=
be
mostly correct.
The applet is acting as a "passkey-agent". To do this, it registers itself =
as
one at the hcid (via DBus).
If hcid now detects that it needs a passkey, it asks the registered passkey
agent for the passkey (via a DBus signal), the passkey-agent then asks the
user and provides the passkey to hcid (again via DBus).
hcid then uses the passkey to generate a link key, which is stored on the d=
isk
and later used for subsequent connections to the same device.
If there is no passkey agent registered at the time the passkey is needed,
access is denied.
Question that popped up, but that i can't answer offhand:
- can there be more than one passkey agent at a time? (not sure, but why no=
t?)
- where can i find a sample implementation? (answer: in passkey-agent.c)
> It is perhaps difficult not only for me to accept working bluez =
> components without understanding the underlying mechanisms.
This is why it is a good idea to put the "Big Picture Document" together :-)
Thanks,
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-19 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 11:45 [Bluez-users] Connecting to a two-way headset Peter Wurmsdobler
2008-02-19 2:49 ` Leszek Koltunski
2008-02-19 20:26 ` Stefan Seyfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-17 17:07 mountain rides
2008-02-18 2:38 ` Leszek Koltunski
2008-02-18 15:25 ` Guillaume Bedot
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=47BB3B76.6000302@suse.de \
--to=seife@suse.de \
--cc=bluez-users@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