public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: PIN Helper
Date: Tue, 15 Sep 2009 18:24:06 +0200	[thread overview]
Message-ID: <4AAFBFA6.70007@binarywings.net> (raw)
In-Reply-To: <20090915061104.GA20323@jh-x301>

Johan Hedberg schrieb:
> Hi,
> 
> On Tue, Sep 15, 2009, Kartikey Parmar wrote:
>> I have installed bluez-4.52 with linux-2.6.30 on my arm board. I m
>> trying to connect to headset but because of unavailability of linkkey
>> I can't obtain connection.
>>
>> Is there any provision for linkkey generation for pairing in
>> bluez-4.52? Any tool available that can be run on arm-linux board? I
>> can't go for bluez-gnome else I need to install all its dependencies
>> which will add more load in terms of memory.
> 
> You could try one of the sample agents that come with BlueZ, i.e.
> test/simple-agent or test/agent.c. Or then just write your own agent to
> suite your needs.
> 

Just out of curiosity: Why does Bluez no longer provide any kind of
deamon as a pin helper any more?

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 lack of such functionality is one of the reasons which still keep me
on bluez-2.25. (lack of user documentation and howtos for >=3.x is the
other reason, by the way).

Just my two cents,
Florian Philipp

  reply	other threads:[~2009-09-15 16:24 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 [this message]
2009-09-15 16:58     ` Johan Hedberg
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=4AAFBFA6.70007@binarywings.net \
    --to=lists@binarywings.net \
    --cc=linux-bluetooth@vger.kernel.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