All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Security mode 3 pairing acceptor broken with current bluetooth-testing
Date: Sat, 9 May 2009 02:49:02 +0300	[thread overview]
Message-ID: <20090508234902.GA6615@jh-x301> (raw)

Hi Marcel,

I'm getting the following with latest bluetooth-testing kernel when
accepting a connection when either device is in security mode 3:

$ hcidump -V -r secmode3-acp.dump
HCI sniffer - Bluetooth packet analyzer ver 1.42
btsnoop version: 1 datalink type: 1002
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:24:7D:XX:XX:XX class 0x5a020c type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:24:7D:XX:XX:XX role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:24:7D:XX:XX:XX role 0x00
    Role: Master
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:24:7D:XX:XX:XX
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr 00:24:7D:XX:XX:XX
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 00:24:7D:XX:XX:XX
> HCI Event: PIN Code Request (0x16) plen 6
    bdaddr 00:24:7D:XX:XX:XX
< HCI Command: Create Connection Cancel (0x01|0x0008) plen 6
    bdaddr 00:24:7D:XX:XX:XX
> HCI Event: Command Complete (0x0e) plen 10
    Create Connection Cancel (0x01|0x0008) ncmd 1
    status 0x00 bdaddr 00:24:7D:XX:XX:XX
> HCI Event: Connect Complete (0x03) plen 11
    status 0x02 handle 12 bdaddr 00:24:7D:XX:XX:XX type ACL encrypt 0x00
    Error: Unknown Connection Identifier

As you see, the kernel is sending "Create Connection Cancel" for this acceptor
use case even though it's a connection initiator command. It comes immediately
after the PIN code request when bluetoothd is waiting for the UI to respond.
I'll try to find some time to investigate this during the weekend but decided
to also post it here in case you know a simple fix for it.

Johan

             reply	other threads:[~2009-05-08 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 23:49 Johan Hedberg [this message]
2009-05-09  0:08 ` Security mode 3 pairing acceptor broken with current bluetooth-testing Marcel Holtmann
2009-05-09  8:59   ` Johan Hedberg
2009-05-09 16:53     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090508234902.GA6615@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.