From: Radek Rurarz <fotopiper@o2.pl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PIN helper
Date: Thu, 9 Mar 2006 19:29:53 +0100 [thread overview]
Message-ID: <20060309192953.52ee8c2e.fotopiper@o2.pl> (raw)
In-Reply-To: <20060309061255.GC4516@beta.private.mielke.cc>
On Thu, 9 Mar 2006 01:12:55 -0500
Dave Mielke <dave@mielke.cc> wrote:
> [quoted lines by Radek Rurarz on 2006/03/09 at 07:06 +0100]
>=20
> >A simpler method would be to relly on another pinhelper (for
> >instance one from the bluez-utlis) set in a config file.. juts pass
> >the arguments to it.. and see if it returns a propper pin.. if not
> >fall back to the internal methods (promp if allowed, the pin file
> >shoud be checked first).
>=20
> Do you think it should be just one, or should multiple specifications
> of the option accumulate a set of helpers to try?
Good question..
For security reasons an simplicyty... one is a good idea.
But having an option to try more then one is more universal (but not
nessesary).
If it's not a big problem (both for you to implement and for the system
to compute..) it would be a nice feature.
=20
> >Sorry, didn't noticed that... I need to work on my sh skills ;)
>=20
> I'm grateful that you didn't as that gave me the idea to document the
> "feature".
It would be nice ;) still the bluz is poorly documented as whole.. an
you're prepering the helper... The documentation is usually prepered
after something is ready ;)
Ps.
I prefer a working program, then a problematic one with documentation ;)
My regards.
Ps.
Sorry for any spelling mistakes...
--=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
next prev parent reply other threads:[~2006-03-09 18:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 21:19 [Bluez-devel] PIN helper Radek
2006-03-08 21:40 ` 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 [this message]
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=20060309192953.52ee8c2e.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.