Re: [Bluez-devel] Pin for an outgoing connection

Valentine Sinitsyn
2006-10-23T14:02:27Z

Hi Marcel,

> > So, if I understood correctly, specifying pin in the hcid.conf only
> > affects incoming connection (i.e., for user's point of view "my
> > computer's pin" is stored there) and pin for outgoing connection ("my
> > phone's pin" form user perspective) is always asked via D-BUS and
> > there is no way to specify it in the config? So hcid manpage should be
> > fixed. Is passkey-agent the only pin agent available now?
>
> actually in the current default configuration, the PIN code will be
> always requested via the passkey agent. It is the most secure way and in
> case no passkey agent is running the authentication request will be
> automatically rejected.
Yes, that's exactly what I'm observing.

> Besides the passkey-agent.c example (yes, it is an example only), you
> can use bluetooth-applet from bluez-gnome if you are running the GNOME
> desktop environment. Otherwise you have to write one by yourself, but
> that is not hard at all. It is actually kinda simple.
Sure - I have some experience developing D-BUS applications. ;-) I
only guess that (as we already have passkey-agent for GNOME and I'm
running KDE) this should be done within the kdebluetooth framework so
I'd better ask kdebluetooth team if they need one (and not developing
it till now, which would be surprise for me).

Thank you very much for the explanation and please fix manpage for hid.conf ;-)

--
Regards,
Valentine Sinitsyn