All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radek Rurarz <fotopiper@o2.pl>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] New PIN helper, how to include with BlueZ?
Date: Sat, 11 Mar 2006 19:06:06 +0100	[thread overview]
Message-ID: <20060311190606.236f7cbd.fotopiper@o2.pl> (raw)

Hello,
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.

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.

As can be seen above this gives more choices on chow to handle new
devices (list, prompt, secondary helper).

--=20
Rados=B3aw Rurarz
Warsaw Poland
GG: 7249330


-------------------------------------------------------
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-11 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-11 18:06 Radek Rurarz [this message]
2006-03-12 17:50 ` [Bluez-devel] New PIN helper, how to include with BlueZ? Marcel Holtmann
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=20060311190606.236f7cbd.fotopiper@o2.pl \
    --to=fotopiper@o2.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.