pand seem to ignore any pin configurations

Bluez-users Rainer Dorsch 2 participants 10 messages May 7, 2005 – May 8, 2005 Bluetooth drivers

Share & tools

Rainer Dorsch

author

2005-05-07 20:03 UTC #0 lore raw

Hello,

I have setup a PAN network with a NAP (bluez-utils 2.15/kernel 2.6.7) and a PANU (bluez-utils/kernel-2.6.8). Each has an usb bt dongle and runs Debian sarge. Surprisingly, they seem to ignore any pin configuration. If there is good documentation on this somewhere, I would be happy with a pointer.

My assumption is that the PANU provides a PIN and NAP needs to confirm it.

My first problem is that I do not understand, where to provide a PIN on the PANU.

NAP has this configuration:

silverboxy:~# cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# PIN helper
# pin_helper /usr/bin/bluez-pin;
pin_helper /usr/local/bin/pin-helper;
# D-Bus PIN helper
#dbus_pin_helper;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x3e0100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept,master;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;

# Authentication and Encryption (Security Mode 3) #auth enable;
#encrypt enable;
}
silverboxy:~#

and the pin is provided by

silverboxy:~# cat  /usr/local/bin/pin-helper
#!/bin/sh

echo "PIN:1234"

silverboxy:~#

No mattter which pin is there the connection setup works.

What is strange here is that auth is commented out in hcid.conf. If I enable that, I get

May  7 21:48:36 topsi pand[9586]: Failed to connect to the SDP server.

Function not implemented(38)

on the PANU side.

Any ideas are welcome.

Thanks,
Rainer

Signature · 16 lines

Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-07 20:35 UTC #1 lore raw

Hi Rainer,

Quoted 10 lines

I have setup a PAN network with a NAP (bluez-utils 2.15/kernel 2.6.7) and a PANU (bluez-utils/kernel-2.6.8). Each has an usb bt dongle and runs Debian sarge. Surprisingly, they seem to ignore any pin configuration. If there is good documentation on this somewhere, I would be happy with a pointer.
My assumption is that the PANU provides a PIN and NAP needs to confirm it.
My first problem is that I do not understand, where to provide a PIN on the PANU.

start pand with --encrypt on the NAP side. While looking at it, I realized that the --auth option is missing. However --encrypt should imply --auth by definition of the Bluetooth specification.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Rainer Dorsch

author

2005-05-07 21:39 UTC #2 lore raw

Hi Marcel,

thanks for the quick reply. Where would I specify the PIN on the PANU? Should pin_helper in hcid.conf provide this? Where would I specify the PIN on the NAP?

There is no --auth for pand:

silverboxy:~# pand -h
Bluetooth PAN daemon version 2.15
Usage:
        pand <options>
Options:
        --show --list -l          Show active PAN connections
        --listen -s               Listen for PAN connections
        --connect -c <bdaddr>     Create PAN connection
        --autozap -z              Disconnect automatically on exit
        --search -Q[duration]     Search and connect
        --kill -k <bdaddr>        Kill PAN connection
        --killall -K              Kill all PAN connections
        --role -r <role>          Local PAN role (PANU, NAP, GN)
        --service -d <role>       Remote PAN service (PANU, NAP, GN)
        --ethernet -e <name>      Network interface name
        --device -i <bdaddr>      Source bdaddr
        --nosdp -D                Disable SDP
        --encrypt -E              Enable encryption
        --secure -S               Secure connection
        --master -M               Become the master of a piconet
        --nodetach -n             Do not become a daemon
        --persist -p[interval]    Persist mode
        --cache -C[valid]         Cache addresses
        --pidfile -P <pidfile>    Create PID file
silverboxy:~#

Do I need

        # Authentication and Encryption (Security Mode 3)
        auth enable;
        encrypt enable;

in the device section of /etc/bluetooth/hcid.conf?

When I do have them and the --encrypt option for pand on the NAP

rd@silverboxy:~$ ps uaxwww|grep pand|grep -v grep
root     15840  0.0  0.1  1548  536 ?        Ss   23:32   0:00 /usr/bin/pand 
--encrypt --listen --persist --role NAP --pidfile /var/run/pand.pid
rd@silverboxy:~$

I still get pinless authentification (or they somehow match, though I tried to make them different in all files).

Thanks,
Rainer

Am Samstag, 7. Mai 2005 22:35 schrieb Marcel Holtmann:

Quoted 35 lines

Hi Rainer,
Quoted 7 lines
I have setup a PAN network with a NAP (bluez-utils 2.15/kernel 2.6.7) and a PANU (bluez-utils/kernel-2.6.8). Each has an usb bt dongle and runs Debian sarge. Surprisingly, they seem to ignore any pin configuration. If there is good documentation on this somewhere, I would be happy with a pointer.
Quoted 5 lines
My assumption is that the PANU provides a PIN and NAP needs to confirm it.
My first problem is that I do not understand, where to provide a PIN on the PANU.
start pand with --encrypt on the NAP side. While looking at it, I realized that the --auth option is missing. However --encrypt should imply --auth by definition of the Bluetooth specification.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Signature · 16 lines

Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-07 22:02 UTC #3 lore raw

Hi Rainer,

Quoted 3 lines

thanks for the quick reply. Where would I specify the PIN on the PANU? Should pin_helper in hcid.conf provide this? Where would I specify the PIN on the NAP?

if you use "security user" then the PIN is provided through the PIN helper script.

Quoted 1 line

There is no --auth for pand:

You read my answer, do you? I said that I realized that it is missing and that you should use --encrypt instead. It is fixed in the CVS.

Quoted 7 lines

Do I need
        # Authentication and Encryption (Security Mode 3)
        auth enable;
        encrypt enable;
in the device section of /etc/bluetooth/hcid.conf?

If you know what security mode 3 means, feel free to use it otherwise you might wanna look into the Bluetooth specification first. And btw there is a reason why it is commented out ;)

Quoted 9 lines

When I do have them and the --encrypt option for pand on the NAP
rd@silverboxy:~$ ps uaxwww|grep pand|grep -v grep
root     15840  0.0  0.1  1548  536 ?        Ss   23:32   0:00 /usr/bin/pand 
--encrypt --listen --persist --role NAP --pidfile /var/run/pand.pid
rd@silverboxy:~$ 
I still get pinless authentification (or they somehow match, though I tried to make them different in all files).

Check with "hcidump -X -V" is you are not already paired and both sides only authenticate with a link key. You can also use "hcitool auth" do trigger the authentication by hand.

Regards

Marcel

Rainer Dorsch

author

2005-05-08 13:08 UTC #4 lore raw

Hi Marcel,

thanks again for the immediate answer.

Am Sonntag, 8. Mai 2005 00:02 schrieb Marcel Holtmann:

Quoted 8 lines

Hi Rainer,
Quoted 3 lines
thanks for the quick reply. Where would I specify the PIN on the PANU? Should pin_helper in hcid.conf provide this? Where would I specify the PIN on the NAP?
if you use "security user" then the PIN is provided through the PIN helper script.

and auto just uses the pin in

/etc/bluetooth/pin ?

Then all the helper scripts in the net which print out

PIN: <content of /etc/bluetooth/pin>

are nonsense?

Examples are here http://www.triptico.com/software/bluetooth.html and here
http://gentoo-wiki.com/HOWTO_The_host-to-host_Bluetooth

When security user on NAP and PANU, is pin_helper called both on PANU and NAP and the pins just should be the same?

Quoted 5 lines

Quoted 2 lines
There is no --auth for pand:
You read my answer, do you? I said that I realized that it is missing and that you should use --encrypt instead. It is fixed in the CVS.

I apologize for not carefully reading.

Quoted 7 lines

Do I need

        # Authentication and Encryption (Security Mode 3)
        auth enable;
        encrypt enable;

Quoted 5 lines

Quoted 1 line
in the device section of /etc/bluetooth/hcid.conf?
If you know what security mode 3 means, feel free to use it otherwise you might wanna look into the Bluetooth specification first. And btw there is a reason why it is commented out ;)

Thanks. I commented it out again ;-)

Quoted 8 lines

When I do have them and the --encrypt option for pand on the NAP

rd@silverboxy:~$ ps uaxwww|grep pand|grep -v grep
root     15840  0.0  0.1  1548  536 ?        Ss   23:32   0:00
/usr/bin/pand --encrypt --listen --persist --role NAP --pidfile
/var/run/pand.pid rd@silverboxy:~$

Quoted 6 lines

Quoted 2 lines
I still get pinless authentification (or they somehow match, though I tried to make them different in all files).
Check with "hcidump -X -V" is you are not already paired and both sides only authenticate with a link key. You can also use "hcitool auth" do trigger the authentication by hand.

hcitool auth is pretty transparent. When I dump on the PANU and run hcitool auth <PANU-addr> on the NAP, I get no output at all from hcidump, when I run hcitool auth <NAP-addr>, I get (again from hcidump on PANU):

< HCI Command: Authentication Requested (0x01|0x0011) plen 2
0000: 29 00 ).

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Auth Complete (0x06) plen 3

    status 0x00 handle 41

Hmm....is pairing persistent over rebooting one or both systems (NAP: security auto and PANU: security user)? At least that is what I did and I did not enter a password. pin_helper is bluez-pin on the PANU, so I expect that PANU should have querried for a password in any case.

Replugging the usb bt dongle restarts bluez-utils. Is pairing persistent over restarting bluez-utils?

Is it ok that pand on the PANU dies after connection establishment?

root 4296 0.0 0.2 1548 492 ? S< 14:48 0:00 /usr/bin/pand
--nodetach --role PANU --search --encrypt
root 4303 0.0 0.2 1548 472 pts/2 S+ 14:49 0:00 grep pand

topsi:~# ps uaxwww|grep pand
root      4397  0.0  0.2  1548  472 pts/2    S+   14:50   0:00 grep pand
topsi:~#

I did an hcidump after replugging the bt usb dongle on PANU, hcidump is also on PANU:

topsi:~# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.17
Can't attach to device hci0. No such device(19)
topsi:~# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
  0000: 33 8b 9e 0a 0a                                    3....

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Inquiry (0x01|0x0001) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Inquiry Result (0x02) plen 15

    bdaddr 00:04:61:82:24:9F clkoffset 0x2945 class 0x3e0100

Quoted 1 line

HCI Event: Inquiry Complete (0x01) plen 1

    status 0x00

< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 9f 24 82 61 04 00 18 cc 01 00 45 a9 01 .$.a......E..

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Create Connection (0x01|0x0005) status 0x00 ncmd 1

< HCI Command: Write Scan Enable (0x03|0x001a) plen 1
0000: 03 .

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Scan Enable (0x03|0x001a) ncmd 1
0000: 00 .
< HCI Command: Write Authentication Enable (0x03|0x0020) plen 1
0000: 00 .

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Authentication Enable (0x03|0x0020) ncmd 1
0000: 00 .
< HCI Command: Write Authentication Enable (0x03|0x0020) plen 1
0000: 00 .

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Authentication Enable (0x03|0x0020) ncmd 1
0000: 00 .
< HCI Command: Write Encryption Mode (0x03|0x0022) plen 1
0000: 00 .

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Encryption Mode (0x03|0x0022) ncmd 1
0000: 00 .
< HCI Command: Write Class of Device (0x03|0x0024) plen 3
0000: 00 01 3e ..>

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Class of Device (0x03|0x0024) ncmd 1
0000: 00 .
< HCI Command: Write Local Name (0x03|0x0013) plen 248

  0000: 74 6f 70 73 69 2d 30 00  00 00 00 00 00 00 00 00  topsi-0.........
  0010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00f0: 00 00 00 00 00 00 00 00                           ........

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 4

Write Local Name (0x03|0x0013) ncmd 1
0000: 00 .

Quoted 1 line

HCI Event: Role Change (0x12) plen 8

0000: 00 9f 24 82 61 04 00 01 ..$.a...

Quoted 1 line

HCI Event: Link Key Request (0x17) plen 6

0000: 9f 24 82 61 04 00 .$.a..
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 9f 24 82 61 04 00 bf 9c 53 9d f1 8e fb 60 50 c7 .$.a....S....`P.
0010: 11 26 ac e3 16 06 .&....

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

    Link Key Request Reply (0x01|0x000b) ncmd 1
    0000: 00 9f 24 82 61 04 00                              ..$.a..

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

    status 0x00 handle 41 bdaddr 00:04:61:82:24:9F type ACL encrypt 0x01
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 29 00 0f 00 )...

Quoted 1 line

HCI Event: Max Slots Change (0x1b) plen 3

0000: 29 00 05 )..

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

Write Link Policy Settings (0x02|0x000d) ncmd 1
0000: 00 29 00 .).

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 12

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 41 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 41 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 1]
        SDP SS Req: tid 0x0 len 0x8
          pat uuid-16 0x1116 (NAP)
          max 1
          cont 00

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 18

    L2CAP(d): cid 0x0040 len 14 [psm 1]
        SDP SS Rsp: tid 0x0 len 0x9
          count 1
          handle 0x10001
          cont 00
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 15 scid 0x0041

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 12

    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
      Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1691

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
      Success

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 1691
< ACL data: handle 41 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 41 flags 0x02 dlen 11
    L2CAP(d): cid 0x0040 len 7 [psm 15]
      BNEP: Control(0x01|0)
        Setup Req(0x01) size 0x02 dst 0x1116(NAP) src 0x1115(PANU)

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Setup Rsp(0x02) res 0x0000
< ACL data: handle 41 flags 0x02 dlen 20
    L2CAP(d): cid 0x0040 len 16 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x000c
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
< ACL data: handle 41 flags 0x02 dlen 32
    L2CAP(d): cid 0x0040 len 28 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0018
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:00:00:00:01 - 33:33:00:00:00:01
< ACL data: handle 41 flags 0x02 dlen 44
    L2CAP(d): cid 0x0040 len 40 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0024
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01
< ACL data: handle 41 flags 0x02 dlen 44
    L2CAP(d): cid 0x0040 len 40 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0024
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 20

    L2CAP(d): cid 0x0041 len 16 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x000c
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 32

    L2CAP(d): cid 0x0041 len 28 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0018
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 44

    L2CAP(d): cid 0x0041 len 40 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0024
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:00:00:00:01 - 33:33:00:00:00:01
          01:00:5e:00:00:01 - 01:00:5e:00:00:01

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...
< ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 56

    L2CAP(d): cid 0x0041 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:82:24:9f - 33:33:ff:82:24:9f
          33:33:00:00:00:01 - 33:33:00:00:00:01
          01:00:5e:00:00:01 - 01:00:5e:00:00:01

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...
< ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 56

    L2CAP(d): cid 0x0041 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:82:24:9f - 33:33:ff:82:24:9f
          33:33:00:00:00:01 - 33:33:00:00:00:01
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 56

    L2CAP(d): cid 0x0041 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:82:24:9f - 33:33:ff:82:24:9f
          33:33:00:00:00:01 - 33:33:00:00:00:01
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
< ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 02 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...
< ACL data: handle 41 flags 0x02 dlen 44

    L2CAP(d): cid 0x0040 len 40 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0024
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000
< ACL data: handle 41 flags 0x02 dlen 192
< ACL data: handle 41 flags 0x01 dlen 149
    L2CAP(d): cid 0x0040 len 337 [psm 15]
      BNEP: Compressed DestOnly(0x04|0)
        dst ff:ff:ff:ff:ff:ff [proto 0x0800]
        0000: 45 10 01 48 00 00 00 00  40 11 b6 88 c0 a8 02 65  
[email protected]
        0010: ff ff ff ff 00 44 00 43  01 34 f0 c2 01 01 06 
00  .....D.C.4......
        0020: 40 39 63 63 00 00 00 00  00 00 00 00 00 00 00 00  
@9cc............
        0030: 00 00 00 00 00 00 00 00  00 04 61 81 10 da 00 
00  ..........a.....
        0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0100: 00 00 00 00 00 00 00 00  63 82 53 63 35 01 03 
32  ........c.Sc5..2
        0110: 04 c0 a8 02 65 37 07 01  1c 02 03 0f 06 0c ff 
00  ....e7..........
        0120: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0130: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0140: 00 00 00 00 00 00 00 00                           ........

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...
< ACL data: handle 41 flags 0x02 dlen 192
< ACL data: handle 41 flags 0x01 dlen 149

    L2CAP(d): cid 0x0040 len 337 [psm 15]
      BNEP: Compressed DestOnly(0x04|0)
        dst ff:ff:ff:ff:ff:ff [proto 0x0800]
        0000: 45 10 01 48 00 00 00 00  40 11 b6 88 c0 a8 02 65  
[email protected]
        0010: ff ff ff ff 00 44 00 43  01 34 f0 be 01 01 06 
00  .....D.C.4......
        0020: 40 39 63 63 00 04 00 00  00 00 00 00 00 00 00 00  
@9cc............
        0030: 00 00 00 00 00 00 00 00  00 04 61 81 10 da 00 
00  ..........a.....
        0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0100: 00 00 00 00 00 00 00 00  63 82 53 63 35 01 03 
32  ........c.Sc5..2
        0110: 04 c0 a8 02 65 37 07 01  1c 02 03 0f 06 0c ff 
00  ....e7..........
        0120: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0130: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0140: 00 00 00 00 00 00 00 00                           ........

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 2 lines

ACL data: handle 41 flags 0x02 dlen 339
ACL data: handle 41 flags 0x01 dlen 5

    L2CAP(d): cid 0x0041 len 340 [psm 15]
      BNEP: Compressed(0x02|0)
        [proto 0x0800]
        0000: 45 10 01 51 00 00 00 00  40 11 f3 d5 c0 a8 02 01  
E..Q....@.......
        0010: c0 a8 02 65 00 43 00 44  01 3d 71 7b 02 01 06 
00  ...e.C.D.=q{....
        0020: 40 39 63 63 00 04 00 00  00 00 00 00 c0 a8 02 65  
@9cc...........e
        0030: c0 a8 02 01 00 00 00 00  00 04 61 81 10 da 00 
00  ..........a.....
        0040: 00 00 00 00 00 00 00 00  73 69 6c 76 65 72 62 
6f  ........silverbo
        0050: 78 79 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
xy..............
        0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 
00  ................
        0100: 00 00 00 00 00 00 00 00  63 82 53 63 35 01 05 
36  ........c.Sc5..6
        0110: 04 c0 a8 02 01 33 04 00  00 02 58 01 04 ff ff 
ff  .....3....X.....
        0120: 00 1c 04 c0 a8 02 ff 03  04 c0 a8 02 01 0f 13 
6b  ...............k
        0130: 61 74 68 72 69 6e 75 6e  64 72 61 69 6e 65 72 2e  
athrinundrainer.
        0140: 64 65 06 04 c0 a8 01 01  0c 06 74 6f 70 73 69 62  
de........topsib
        0150: ff                                                .
< ACL data: handle 41 flags 0x02 dlen 56
    L2CAP(d): cid 0x0040 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01
< ACL data: handle 41 flags 0x02 dlen 56
    L2CAP(d): cid 0x0040 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01
< ACL data: handle 41 flags 0x02 dlen 56
    L2CAP(d): cid 0x0040 len 52 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Set(0x05) len 0x0030
          ff:ff:ff:ff:ff:ff - ff:ff:ff:ff:ff:ff
          01:00:5e:00:00:01 - 01:00:5e:00:00:01
          33:33:ff:81:10:da - 33:33:ff:81:10:da
          33:33:00:00:00:01 - 33:33:00:00:00:01

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 29 00 01 00 .)...

Quoted 1 line

ACL data: handle 41 flags 0x02 dlen 8

    L2CAP(d): cid 0x0041 len 4 [psm 15]
      BNEP: Control(0x01|0)
        Filter MultAddr Rsp(0x06) res 0x0000

Many thanks,
Rainer

Quoted 17 lines

Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Signature · 16 lines

Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-08 13:36 UTC #5 lore raw

Hi Rainer,

Quoted 10 lines

Quoted 6 lines
Quoted 3 lines
thanks for the quick reply. Where would I specify the PIN on the PANU? Should pin_helper in hcid.conf provide this? Where would I specify the PIN on the NAP?
if you use "security user" then the PIN is provided through the PIN helper script.
and auto just uses the pin in
/etc/bluetooth/pin ?

for incoming connection, yes.

Quoted 5 lines

Then all the helper scripts in the net which print out
PIN: <content of /etc/bluetooth/pin>
are nonsense?

No. Why should they. The script got called and then it reads the pin and writes it to standard out. Think about it ;)

Quoted 2 lines

When security user on NAP and PANU, is pin_helper called both on PANU and NAP and the pins just should be the same?

Yes.

Quoted 6 lines

Quoted 4 lines
Quoted 1 line
There is no --auth for pand:
You read my answer, do you? I said that I realized that it is missing and that you should use --encrypt instead. It is fixed in the CVS.
I apologize for not carefully reading.

No problem. Next version will include it.

Quoted 10 lines

Quoted 10 lines
Quoted 9 lines
When I do have them and the --encrypt option for pand on the NAP
rd@silverboxy:~$ ps uaxwww|grep pand|grep -v grep
root     15840  0.0  0.1  1548  536 ?        Ss   23:32   0:00
/usr/bin/pand --encrypt --listen --persist --role NAP --pidfile
/var/run/pand.pid rd@silverboxy:~$
I still get pinless authentification (or they somehow match, though I tried to make them different in all files).

Quoted 7 lines

Quoted 3 lines
Check with "hcidump -X -V" is you are not already paired and both sides only authenticate with a link key. You can also use "hcitool auth" do trigger the authentication by hand.
hcitool auth is pretty transparent. When I dump on the PANU and run hcitool auth <PANU-addr> on the NAP, I get no output at all from hcidump, when I run hcitool auth <NAP-addr>, I get (again from hcidump on PANU):

Make sure you start "hcidump" as root.

Quoted 4 lines

< HCI Command: Authentication Requested (0x01|0x0011) plen 2
0000: 29 00 ).
Quoted 1 line
HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1

Quoted 8 lines

Quoted 1 line
HCI Event: Auth Complete (0x06) plen 3
    status 0x00 handle 41
Hmm....is pairing persistent over rebooting one or both systems (NAP: security auto and PANU: security user)? At least that is what I did and I did not enter a password. pin_helper is bluez-pin on the PANU, so I expect that PANU should have querried for a password in any case.

The pairing itself is persistent over reboots and also unplugging. The link keys are also cached inside the chip and so Authentication Requested must not always result in asking for the link key or pin code.

Quoted 16 lines

Replugging the usb bt dongle restarts bluez-utils. Is pairing persistent over restarting bluez-utils?
Is it ok that pand on the PANU dies after connection establishment?
root 4296 0.0 0.2 1548 492 ? S< 14:48 0:00 /usr/bin/pand
--nodetach --role PANU --search --encrypt
root 4303 0.0 0.2 1548 472 pts/2 S+ 14:49 0:00 grep pand
topsi:~# ps uaxwww|grep pand
root      4397  0.0  0.2  1548  472 pts/2    S+   14:50   0:00 grep pand
topsi:~# 
I did an hcidump after replugging the bt usb dongle on PANU, hcidump is also on PANU:

Quoted 8 lines

Quoted 1 line
HCI Event: Link Key Request (0x17) plen 6
0000: 9f 24 82 61 04 00 .$.a..
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 9f 24 82 61 04 00 bf 9c 53 9d f1 8e fb 60 50 c7 .$.a....S....`P.
0010: 11 26 ac e3 16 06 .&....
Quoted 1 line
HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Reply (0x01|0x000b) ncmd 1
    0000: 00 9f 24 82 61 04 00                              ..$.a..

It asks for the link key and so you are pairing. To always be asked for the PIN code I think you need to change hcid to allow a mode where you always have to redo the pairing. In this case the Link Key Request must be answered with a Link Key Request Negative Reply. This effect can also be reached by deleted the link key from the local storage.

Regards

Marcel

Rainer Dorsch

author

2005-05-08 15:27 UTC #6 lore raw

Hi Marcel,

Am Sonntag, 8. Mai 2005 15:36 schrieb Marcel Holtmann:

Quoted 9 lines

Quoted 6 lines
Quoted 2 lines
if you use "security user" then the PIN is provided through the PIN helper script.
and auto just uses the pin in
/etc/bluetooth/pin ?
for incoming connection, yes.

Quoted 8 lines

Quoted 5 lines
Then all the helper scripts in the net which print out
PIN: <content of /etc/bluetooth/pin>
are nonsense?
No. Why should they. The script got called and then it reads the pin and writes it to standard out. Think about it ;)

Wouldn't be

security auto

the same as

security user
# PIN helper
# pin_helper /usr/bin/bluez-pin;
pin_helper /usr/local/sbin/mypin

and /usr/local/sbin/mypin, containing

        #!/bin/sh
        PIN=`cat /etc/bluetooth/pin`
        echo "PIN:$PIN"

Quoted 36 lines

Quoted 4 lines
Hmm....is pairing persistent over rebooting one or both systems (NAP:
security auto and PANU: security user)? At least that is what I did and I did not enter a password. pin_helper is bluez-pin on the PANU, so I expect that PANU should have querried for a password in any case.
The pairing itself is persistent over reboots and also unplugging. The link keys are also cached inside the chip and so Authentication Requested must not always result in asking for the link key or pin code.
Quoted 27 lines
Replugging the usb bt dongle restarts bluez-utils. Is pairing persistent over restarting bluez-utils?
Is it ok that pand on the PANU dies after connection establishment?
root 4296 0.0 0.2 1548 492 ? S< 14:48 0:00
/usr/bin/pand --nodetach --role PANU --search --encrypt
root 4303 0.0 0.2 1548 472 pts/2 S+ 14:49 0:00 grep pand
topsi:~# ps uaxwww|grep pand
root      4397  0.0  0.2  1548  472 pts/2    S+   14:50   0:00 grep pand
topsi:~#
I did an hcidump after replugging the bt usb dongle on PANU, hcidump is also
on PANU:
Quoted 1 line
HCI Event: Link Key Request (0x17) plen 6
0000: 9f 24 82 61 04 00 .$.a..
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 9f 24 82 61 04 00 bf 9c 53 9d f1 8e fb 60 50 c7
.$.a....S....`P. 0010: 11 26 ac e3 16 06
.&....
Quoted 1 line
HCI Event: Command Complete (0x0e) plen 10

Quoted 8 lines

Quoted 2 lines
    Link Key Request Reply (0x01|0x000b) ncmd 1
    0000: 00 9f 24 82 61 04 00                              ..$.a..
It asks for the link key and so you are pairing. To always be asked for the PIN code I think you need to change hcid to allow a mode where you always have to redo the pairing. In this case the Link Key Request must be answered with a Link Key Request Negative Reply. This effect can also be reached by deleted the link key from the local storage.

Not asking for a PIN each time is actually fine (persisten pairing is a nice invention;-). I just want to check that the system really wants to see a PIN when a new device comes in.

Are you saying when I delete

/etc/bluetooth/link_key

on both NAP and PANU I should be askef for a password?

Thanks,
Rainer

Quoted 17 lines

Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Signature · 16 lines

Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-08 15:46 UTC #7 lore raw

Hi Rainer,

Quoted 29 lines

Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
if you use "security user" then the PIN is provided through the PIN helper script.
and auto just uses the pin in
/etc/bluetooth/pin ?
for incoming connection, yes.
Quoted 8 lines
Quoted 5 lines
Then all the helper scripts in the net which print out
PIN: <content of /etc/bluetooth/pin>
are nonsense?
No. Why should they. The script got called and then it reads the pin and writes it to standard out. Think about it ;)
Wouldn't be
security auto
the same as
security user
# PIN helper
# pin_helper /usr/bin/bluez-pin;
pin_helper /usr/local/sbin/mypin

Quoted 7 lines

and /usr/local/sbin/mypin, containing

        #!/bin/sh
        PIN=`cat /etc/bluetooth/pin`
        echo "PIN:$PIN"

in this special case, yes. But in most cases you use a graphical PIN helper.

Quoted 49 lines

Quoted 36 lines
Quoted 4 lines
Hmm....is pairing persistent over rebooting one or both systems (NAP:
security auto and PANU: security user)? At least that is what I did and I did not enter a password. pin_helper is bluez-pin on the PANU, so I expect that PANU should have querried for a password in any case.
The pairing itself is persistent over reboots and also unplugging. The link keys are also cached inside the chip and so Authentication Requested must not always result in asking for the link key or pin code.
Quoted 27 lines
Replugging the usb bt dongle restarts bluez-utils. Is pairing persistent over restarting bluez-utils?
Is it ok that pand on the PANU dies after connection establishment?
root 4296 0.0 0.2 1548 492 ? S< 14:48 0:00
/usr/bin/pand --nodetach --role PANU --search --encrypt
root 4303 0.0 0.2 1548 472 pts/2 S+ 14:49 0:00 grep pand
topsi:~# ps uaxwww|grep pand
root      4397  0.0  0.2  1548  472 pts/2    S+   14:50   0:00 grep pand
topsi:~#
I did an hcidump after replugging the bt usb dongle on PANU, hcidump is also
on PANU:
Quoted 1 line
HCI Event: Link Key Request (0x17) plen 6
0000: 9f 24 82 61 04 00 .$.a..
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 9f 24 82 61 04 00 bf 9c 53 9d f1 8e fb 60 50 c7
.$.a....S....`P. 0010: 11 26 ac e3 16 06
.&....
Quoted 1 line
HCI Event: Command Complete (0x0e) plen 10
Quoted 8 lines
Quoted 2 lines
    Link Key Request Reply (0x01|0x000b) ncmd 1
    0000: 00 9f 24 82 61 04 00                              ..$.a..
It asks for the link key and so you are pairing. To always be asked for the PIN code I think you need to change hcid to allow a mode where you always have to redo the pairing. In this case the Link Key Request must be answered with a Link Key Request Negative Reply. This effect can also be reached by deleted the link key from the local storage.
Not asking for a PIN each time is actually fine (persisten pairing is a nice invention;-). I just want to check that the system really wants to see a PIN when a new device comes in.

Quoted 5 lines

Are you saying when I delete
/etc/bluetooth/link_key
on both NAP and PANU I should be askef for a password?

Yes. And with bluez-utils-2.16 the link key storage has been changed. Check the mailing list archive for more details.

Regards

Marcel

Rainer Dorsch

author

2005-05-08 16:24 UTC #8 lore raw

Hi Marcel,

Am Sonntag, 8. Mai 2005 17:46 schrieb Marcel Holtmann:

Quoted 11 lines

Quoted 9 lines
Not asking for a PIN each time is actually fine (persisten pairing is a nice invention;-). I just want to check that the system really wants to see a PIN when a new device comes in.
Are you saying when I delete
/etc/bluetooth/link_key
on both NAP and PANU I should be askef for a password?
Yes. And with bluez-utils-2.16 the link key storage has been changed.

Worked excellent, thanks. Are the link keys valid forever or do they have an expiration date? I.e. if is do "security user" may it happen that bluez simply stops working (because e.g. bluez is started before X and I won't notice why until I figured out that the link key expired)

Quoted 1 line

Check the mailing list archive for more details.

I saw that before, "link key storage" and bluez does not have many hits on google ;-)

Many thanks,
Rainer

Signature · 16 lines

Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-08 16:31 UTC #9 lore raw

Hi Rainer,

Quoted 8 lines

Quoted 8 lines
Quoted 8 lines
Not asking for a PIN each time is actually fine (persisten pairing is a nice invention;-). I just want to check that the system really wants to see a PIN when a new device comes in.
Are you saying when I delete
/etc/bluetooth/link_key

Quoted 8 lines

Quoted 3 lines
Quoted 1 line
on both NAP and PANU I should be askef for a password?
Yes. And with bluez-utils-2.16 the link key storage has been changed.
Worked excellent, thanks. Are the link keys valid forever or do they have an expiration date? I.e. if is do "security user" may it happen that bluez simply stops working (because e.g. bluez is started before X and I won't notice why until I figured out that the link key expired)

the link key don't expires. However using --secure with a recent kernel you can force a change of the link key every time the connection was successful.

Regards

Marcel