Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] New PIN helper, how to include with BlueZ?
Date: Sun, 12 Mar 2006 18:50:09 +0100	[thread overview]
Message-ID: <1142185809.4620.3.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20060311190606.236f7cbd.fotopiper@o2.pl>

Hi Radek,

> a new PIN helper has been born, and I think it's time to include it in
> the BlueZ packages (including source packages) either as a default
> helper, or as an option. The problem is neither me, nor the author have
> a good sense of how such things happen for BlueZ.

you post a patch to mailing list and it will be discussed and if it is a
sane approach it will be included. As simple as that.

> For those who haven't fallowed our discussion I will gave a short
> summary of the situation:
> 
> Dave Mielke has been working for some time on a new PIN helper for
> BlueZ, one that deals in a more complex, and in my opinion complete way,
> with the problem.
> 
> The basic approach is to have a list of pins and device addresses in a
> file, form which the helper will extract the correct PIN. If the device
> is not on the list a prompt is started on a new terminal, that asks for
> PIN (giving all the standard information). In case the terminal prompt
> is not welcomed, a secondary helper can be called (for instance the
> python script already shipped with BlueZ, or other for KDE/GPE/OPIE or
> any other). The prompt can be fully disabled. The script can be
> configured either with a config file, or by command line parameters.

The /var/lib/bluetooth/<bdaddr>/pincodes file is supported for outgoing
connection for quite some time. The default /etc/bluetooth/pin has been
already removed and the complete PIN helper script support will be
remove really soon, too. The new way for the having a flexible way of
PIN handling will be over D-Bus. At some not so far point in the future
the bluez-utils package will depend on D-Bus anyway.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-03-12 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-11 18:06 [Bluez-devel] New PIN helper, how to include with BlueZ? Radek Rurarz
2006-03-12 17:50 ` Marcel Holtmann [this message]
2006-03-12 19:13   ` Radek Rurarz
2006-03-12 19:32     ` Marcel Holtmann
2006-03-12 19:51       ` Radek Rurarz
2006-03-12 23:54         ` Marcel Holtmann
2006-03-12 20:40       ` Radek Rurarz
2006-03-12 23:55         ` 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=1142185809.4620.3.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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