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 20:32:40 +0100	[thread overview]
Message-ID: <1142191960.4620.8.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20060312201345.1846901c.fotopiper@o2.pl>

Hi Radek,

> > 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.
> 
> Hmm.. I see that BlueZ is even less documented then I thought.
> What is the syntax of the file?
> PS. I'm using the current stable version, and the /etc/bluetooth/pin is
> still there.. so I suppose it's still rather for the future. (but
> rather not far future).

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.

The syntax of the pincodes file is easy. It is a BD_ADDR and PIN code
pair per line. Like the names file etc.

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

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.

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 19:32 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 [this message]
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=1142191960.4620.8.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