From: Johan Hedberg <johan.hedberg@gmail.com>
To: Florian Philipp <lists@binarywings.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: PIN Helper
Date: Tue, 15 Sep 2009 19:58:54 +0300 [thread overview]
Message-ID: <20090915165854.GA6550@jh-x301> (raw)
In-Reply-To: <4AAFBFA6.70007@binarywings.net>
Hi,
On Tue, Sep 15, 2009, Florian Philipp wrote:
> Just out of curiosity: Why does Bluez no longer provide any kind of
> deamon as a pin helper any more?
Isn't that exactly what the two command line based agents are if you run
them in the background and modify them to always accept pairing requests?
Or am I misunderstanding your question? Note that we can't anymore have
interfaces which just deal with a simple PIN. Bluetooth 2.1 SSP brings
along it's own set of callbacks that need handling and any interface that
we define (be it a config file, D-Bus or something else) needs to take
that into account.
> I mean, it's not like Bluetooth itself is limited to interactive systems
> which rightly demand graphical interfaces nowadays. Stuff like NAP is a
> classic client-server situation in which you don't want to use Gnome or
> KDE apps on the server side and maybe not even on the client side.
The current agent interface design doesn't restrict you in any way to
interactive systems. It merely exports the pairing callbacks from
bluetoothd to an external process. bluetoothd doesn't care if that process
does some interactive stuff or not.
Johan
next prev parent reply other threads:[~2009-09-15 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 6:01 PIN Helper Kartikey Parmar
2009-09-15 6:11 ` Johan Hedberg
2009-09-15 16:24 ` Florian Philipp
2009-09-15 16:58 ` Johan Hedberg [this message]
2009-09-16 15:44 ` Florian Philipp
2009-09-16 16:41 ` Johan Hedberg
2009-09-16 18:39 ` Florian Philipp
2009-09-17 19:49 ` Luiz Augusto von Dentz
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=20090915165854.GA6550@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lists@binarywings.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