From: Radek Rurarz <fotopiper@o2.pl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] New PIN helper, how to include with BlueZ?
Date: Sun, 12 Mar 2006 20:51:57 +0100 [thread overview]
Message-ID: <20060312205157.1092b7d7.fotopiper@o2.pl> (raw)
In-Reply-To: <1142191960.4620.8.camel@aeonflux.holtmann.net>
On Sun, 12 Mar 2006 20:32:40 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:
> the /etc/bluetooth/pin support is removed from the current CVS. And I
> even removed the PIN helper script support completely. So it is the
> near future with the next blue-utils release which has been targeted
> for in two weeks.
>=20
> The syntax of the pincodes file is easy. It is a BD_ADDR and PIN code
> pair per line. Like the names file etc.
Thank you.
Will this stay for the next releses, or is it only a temporary solution?
=20
> > Great, and what about those systems where d-bus is not present?
> > I hope the D-Bus will still be complemented by some list of devices
> > and pins.
>=20
> And what kind of system should that be? All desktop systems are using
> D-Bus and even the Nokia 770 and the new platform from PalmSource are
> supporting it by default. So no reason to use something different than
> D-Bus for PIN handling.
Well, I'm not using D-Bus on WIndow Maker, Opie has no D-bus support
(for now). But I don't mean interactive systems. Rather those which
either have no X, or have no direct input methods at all (home server
sollusions, no screen, no keyboard).
I'm using an old PC as an BT gateway for couple of PDAs.
The truth is that, both for WM and my small gateway, I only need the
device-pin list and a way to disable any kind of prompt for PIN
for unknown devices.
If the support for the pincodes file is a permanent sollusion (one that
will remain in the next relese) then the D-Bus approach is as good for
me, as any other one.
My regards.
--=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-12 19:51 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
2006-03-12 19:13 ` Radek Rurarz
2006-03-12 19:32 ` Marcel Holtmann
2006-03-12 19:51 ` Radek Rurarz [this message]
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=20060312205157.1092b7d7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox