Re: [Bluez-devel] Suggesting bluez_pinhelper

Marcel Holtmann
2007-05-27T16:36:36Z

Hi Gilboa,

> I'm currently trying to get kdebluetooth reviewed into Fedora Core (and
> RHEL).
> As some of you may be aware, the current version of kdebluetooth has no
> support for recent (>= 3.9) bluez DBUS interface.
> As an interim solution I decided to write a small wrapper that can be
> used as a bridge between kdebluetooth's kbluepin and bluez-utils 3.9
> (running on the about to be released F7) - basing my work around
> bluez-utils' passkey-agent.
> While working on it I decided to further expand it - making it
> configurable and script-able which in turns, makes it entirely possible
> to create passkey dialog boxes in non-X modes (using 'dialog') or in
> low-end machines with minimal WM's (using 'zenity' in
> IceWM/Fluxbox/etc).
>
> As it stands I got two options:
> A. Use this code as a stop-gate until qt-dbus + kdebluetooth is released
> (KDE 4?) maintaining this code as a Fedora-only blob.
> B. If its of any use to anyone (read, you), get it submitted into
> bluez-utils while maintaining it (and expending it - if so required)
> upstream.

take this up with the KDE Bluetooth guys since it the Bluetooth support
for KDE 3.x got basically abandoned. It is their job to actually fix it
and provide whatever they need to make Bluetooth working. I am not
really open for crazy hacks. The passkey-agent.c source code is mainly
an example on how to write a passkey agent and was used for initial
testing.

Regards

Marcel