Re: [Bluez-users] Totally confused

manojt ambe
2006-08-16T14:27:50Z

[-- Attachment #1.1: Type: text/plain, Size: 3530 bytes --]

I modified /usr/local/etc/dbus-1/system.conf as below. After this the pin problem went away. I am using bluez 3.1 and dbus 0.62. Pls find system.conf attached.

<!-- This is included last so local configuration can override what's
in this standard file -->
<include ignore_missing="yes">/etc/dbus-1/system.d/bluez-hcid.conf</include>

thanks,
Manoj

redondos <redondos@gmail.com> wrote:
On Wed, Aug 16 09:18, Rui Pedro Lopes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> redondos wrote:
> > Have you tried following the Gentoo wiki? You're probably not using
> > Gentoo, but they are well-known for providing pretty good documentation
> > to the open source community.
> >
> > http://www.gentoo-wiki.com/HOWTO_use_a_bluetooth_headset
> Yap. Actually, I'm using debian...
> >
> > About the PIN code: have you configured a pin helper correctly in
> > hcid.conf? It's pretty simple, you can just write a shell script:
> >
> > #!/bin/sh
> > echo "PIN:1234
> >
> > Make it executable, then edit hcid.conf with the line:
> >
> > pin_helper /path/to/the/script
> Yes, I have tried that. Here is the syslog messages:
>
> Aug 16 09:13:20 tash hcid[7714]: Bluetooth HCI daemon
> Aug 16 09:13:20 tash hcid[7714]: Unknown option 'pin_helper' line 27
> Aug 16 09:13:20 tash hcid[7714]: syntax error line 27
> Aug 16 09:13:20 tash sdpd[7716]: Bluetooth SDP daemon
> Aug 16 09:13:20 tash hidd[7718]: Bluetooth HID daemon
> Aug 16 09:13:20 tash hcid[7714]: Register path:/org/bluez fallback:1
> Aug 16 09:13:20 tash hcid[7714]: Device hci0 has been added
> Aug 16 09:13:21 tash hcid[7714]: Starting security manager 0
> Aug 16 09:13:21 tash hcid[7714]: Can't write inquiry mode for hci0:
> Input/output error (5)
> Aug 16 09:13:21 tash hcid[7714]: Register path:/org/bluez/hci0 fallback:0
>
>
>
> Apparently, pin_helper is not available...

I forgot the ';' at the end of the line. Did you add that? Can we see
your hcid.conf at its full extent?

> Here is what the Debian maintainer added to the documentation:
>
>
> PIN (or passkey) management
> - ---------------------------
> since bluez 3.0 the old pin_helper script has been replaced by
> the dbus interface. To add a default passkey for every outgoing
> request (e.g. the old /etc/bluetooth/pin file) drop it into
> /etc/bluetooth/passkeys/default. (e.g. echo "1234" >
> /etc/bluetooth/passkeys/default )
> To add a passkey for a specific outgoing connection replace default
> with the device's address. ( /etc/default/passkeys/aa:bb:cc:dd:ee:ff
> will contain passkey for aa:bb:cc:dd:ee:ff ).
> After adding a passkey you should restart bluetooth with
>
> /etc/init.d/bluetooth restart
>
> and the new passkeys will be registered.
>
>
> I have also tried that and it is not working... do you think it is a
> Debian problem?

Oh, you're using 3.x. I don't know, haven't played with it yet, sorry.

--
redondos
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

---------------------------------
Get your email and more, right on the new Yahoo.com

[-- Attachment #1.2: Type: text/html, Size: 4344 bytes --]

[-- Attachment #2: 3934571641-system.conf --]
[-- Type: application/octet-stream, Size: 2325 bytes --]

<!-- This configuration file controls the systemwide message bus.
Add a system-local.conf and edit that rather than changing this
file directly. -->

<!-- Note that there are any number of ways you can hose yourself
security-wise by screwing up this file; in particular, you
probably don't want to listen on any more addresses, add any more
auth mechanisms, run as a different user, etc. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>


<type>system</type>


<user>messagebus</user>


<fork/>


<pidfile>/usr/local/var/run/messagebus.pid</pidfile>


<auth>EXTERNAL</auth>

<!-- Only listen on a local socket. (abstract=/path/to/socket
means use abstract namespace, don't really create filesystem
file; only Linux supports this. Use path=/whatever on other
systems.) -->
<listen>unix:path=/usr/local/var/run/dbus/system_bus_socket</listen>

<policy context="default">

<deny send_interface="*"/>
<deny receive_interface="*"/>
<deny own="*"/>

<allow user="*"/>

<!-- FIXME I think currently these allow rules are always implicit
even if they aren't in here -->
<allow send_destination="org.freedesktop.DBus"/>
<allow receive_sender="org.freedesktop.DBus"/>

<allow send_requested_reply="true"/>
<allow receive_requested_reply="true"/>
</policy>

<!-- Config files are placed here that among other things, punch
holes in the above policy for specific services. -->
<includedir>system.d</includedir>

<!-- This is included last so local configuration can override what's
in this standard file -->
<include ignore_missing="yes">/etc/dbus-1/system.d/bluez-hcid.conf</include>

<include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

</busconfig>

[-- Attachment #3: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]