All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radek <fotopiper@o2.pl>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] PIN helper
Date: Wed, 8 Mar 2006 22:19:25 +0100	[thread overview]
Message-ID: <20060308221925.17d20407.fotopiper@o2.pl> (raw)

Hello,
from whot I had read in the net there had been some controversies about
the pinhelpers. The d-bus one need d-bus, and the python one need some
extra libs as well as X..
Maybe it was thougt before.. but I would suggest using a different
method. A list of devices with coresponding pins. This gives the
possibilities to have a different pin for different devices (important
especially if you have some that have a fixed pin:0000, not a very
secure idea for a default pin) and possibly a default pin as an option.
A very simple script that does that:

#!/bin/sh
echo "PIN:"$(grep $2 /etc/bluetooth/pins|sed s/.*PIN\://)

Not a very clean solusion (sorry I'm no programer, and my knowledge of
bash/sh is limited) but portable (bysybox suports all that is needed).
The obviously in format:

anything countaining the HWaddress of the device PIN: and the pin

this gives the possibility to have something like this:

00:0E:05:05:04:02; My cat; PIN:0000
00:0E:05:05:04:01; The dog; PIN:1111432334

It would be better if the script checked the files permisions, gave an
option to use a default pin and maybe some logging... But for that my
current sh knowledge is not enough.. sorry :-(

Still I think this is a beeter solusion, a more universal one, then the
ones shiped with bluez now.. which doesn't meen that the current
helpers are not helpful :)

My regards.

-- 
Radoslaw Rurarz
Warsaw Poland


-------------------------------------------------------
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-08 21:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 21:19 Radek [this message]
2006-03-08 21:40 ` [Bluez-devel] PIN helper Dave Mielke
2006-03-08 22:01   ` Radek Rurarz
2006-03-08 22:16     ` Dave Mielke
2006-03-09  5:44       ` Radek Rurarz
2006-03-09  5:55         ` Dave Mielke
2006-03-09  6:06           ` Radek Rurarz
2006-03-09  6:12             ` Dave Mielke
2006-03-09 18:29               ` Radek Rurarz
2006-03-09 19:34                 ` Dave Mielke
2006-03-09 21:55                   ` Radek Rurarz
2006-03-09 22:04                     ` Radek Rurarz
2006-03-10  1:33                       ` Dave Mielke
2006-03-10  7:28                         ` Radek Rurarz
2006-03-10 13:35                           ` Dave Mielke
2006-03-10 18:10                             ` Radek Rurarz
2006-03-10 17:25                           ` Dave Mielke
2006-03-10 18:13                             ` Radek Rurarz
2006-03-10 18:39                               ` Dave Mielke
2006-03-10 19:22                                 ` Radek Rurarz
2006-03-10 20:55                                   ` Dave Mielke
2006-03-10 22:24                                     ` Radek Rurarz
2006-03-10 23:04                                       ` Dave Mielke
2006-03-13  4:08                                         ` KrAnTi KaMbHaMpAtI
2006-03-10 20:56                                   ` Dave Mielke

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=20060308221925.17d20407.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.