Package: bluez-utils
Version: 2.15-1
Severity: important

Reconnecting pand to the access point using auth enable and encrypt
enable in /etc/bluetooth/hcid.conf does not work with the testing
version, downgrading to the stable version resolves the issue. 

I noticed that the new version takes a more structured management
approach to the link key files. The bug only affects reconnecting. If I
delete the link key files, the new version properly uses the pin to
connect to the access point for the first time.

For sake of completeness I should mention that I use a quick and dirty
custom shell script to supply the pin, it is attached below.

  
   Arne Ahrend

  
--

Excerpt from /var/log/daemon.log:

Sep 27 18:29:21 hellas hcid[2788]: Bluetooth HCI daemon
Sep 27 18:29:21 hellas sdpd[2790]: Bluetooth SDP daemon 
Sep 27 18:29:21 hellas hcid[2788]: HCI dev 0 up
Sep 27 18:29:21 hellas hcid[2788]: Starting security manager 0
Sep 27 18:29:26 hellas pand[2813]: Bluetooth PAN daemon version 2.15
Sep 27 18:29:26 hellas pand[2813]: Connecting to 00:04:0E:84:68:C0
Sep 27 18:29:27 hellas hcid[2788]: link_key_request
(sba=00:04:0E:83:EF:E4, dba=00:04:0E:84:68:C0)
Sep 27 18:29:28 hellas hcid[2788]: link_key_notify
(sba=00:04:0E:83:EF:E4)
Sep 27 18:29:28 hellas hcid[2788]: Replacing link key 00:04:0E:83:EF:E4
00:04:0E:84:68:C0
Sep 27 18:29:28 hellas pand[2813]: bnep0 connected


Sep 27 20:32:43 hellas hcid[8394]: Bluetooth HCI daemon
Sep 27 20:32:43 hellas sdpd[8396]: Bluetooth SDP daemon 
Sep 27 20:32:43 hellas hcid[8394]: Starting security manager 0
Sep 27 20:32:43 hellas pand[8401]: Bluetooth PAN daemon version 2.19
Sep 27 20:32:43 hellas pand[8401]: Connecting to 00:04:0E:84:68:C0
Sep 27 20:32:45 hellas hcid[8394]: link_key_request
(sba=00:04:0E:83:EF:E4, dba=00:04:0E:84:68:C0)
Sep 27 20:32:45 hellas pand[8401]: Connect to 00:04:0E:84:68:C0 failed.
Permission denied(13)



/usr/local/bin/bluez-pin.sh: 

#!/bin/sh
#
# Bluetooth PIN helper

PATH=/bin:/usr/bin

if [ $# -lt 2 ]; then
#    echo "$# less than 2"
    exit
fi 

PINFILE=/etc/bluetooth/pin
INOUT=$1
TARGET=$2

PIN=$(grep $TARGET $PINFILE | grep -v "^#" | head -n1 | cut -f2)

echo -e "PIN:$PIN"

# exit 0

    

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-rc2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages bluez-utils depends on:
ii  bluez-pin            0.25-1              Bluetooth PIN helper with D-BUS su
ii  dbus-1               0.23.4-1            simple interprocess messaging syst
ii  libbluetooth1        2.19-1              Library to use the BlueZ Linux Blu
ii  libc6                2.3.5-6             GNU C Library: Shared libraries an
ii  libusb-0.1-4         2:0.1.10a-9.sarge.1 userspace USB programming library
ii  module-init-tools    3.2-pre8-1          tools for managing Linux kernel mo
ii  modutils             2.4.27.0-3          Linux module utilities
ii  sysvinit             2.86.ds1-2          System-V like init

bluez-utils recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to