public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: Marcel Holtmann <marcel@holtmann.org>
Subject: [Bluez-devel] org.bluez.Agent interface vs. org.bluez.PasskeyAgent and org.bluez.AuthorizationAgent
Date: Fri, 27 Jun 2008 15:07:41 -0500	[thread overview]
Message-ID: <025201c8d891$75c10260$6701a8c0@freqonedev> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1477 bytes --]

I would like to test BT 2.1 and SSP, and have installed the updated kernel with patches onto my system.  To make the connection, I have to install or create an Agent that interacts with the BT daemon (currently, hcid), to deal with the pairing issues introduced by the SSSP (Secure "Supposedly Simple" Pairing).  However, it also appears that the DBus interfaces are in flux.

So, what is the future of these; is it the org.bluez.Agent, as described in bluez-utils-3.34/doc/agent-api.txt?  Or is it the old PasskeyAgent and AuthorizationAgent described in hcid/dbus-api.txt?

Also, the daemon/ directory used to contain sample code for a passkey agent and an authorization agent.  If as I assume these need to move over to the .Agent interface, are there plans to provide a design example for these (or a combined agent daemon)?

Has the gnome agent been modified to the "experimental" interface?

When starting the sample passkey agent, it is possible to provide a path that the agent uses as its object path (in function register_agent, with the call to dbus_connection_register_object_path).  I assume that this path is what we would pass to "Adapter.CreatePairedDevice" as the object path of the agent, with the capabilities string.  Am I correct?

Any constraints on what this object path contains (for example: "/com/frequency-one")?  I assume it must be unique and must not clash with the other paths under org.bluez.

Thanks in advance...

David Stockwell

[-- Attachment #1.2: Type: text/html, Size: 2530 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-06-27 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 20:07 David Stockwell [this message]
2008-06-27 21:10 ` [Bluez-devel] org.bluez.Agent interface vs. org.bluez.PasskeyAgent and org.bluez.AuthorizationAgent Johan Hedberg
2008-06-27 22:25   ` Marcel Holtmann

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='025201c8d891$75c10260$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