From: Johan Hedberg <johan.hedberg@gmail.com>
To: fabien dvlt <fabiendvlt@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Security block and Bluez - connection issue with Android
Date: Wed, 26 Sep 2018 14:28:01 +0300 [thread overview]
Message-ID: <20180926112801.GA8013@x1c.lan> (raw)
In-Reply-To: <CAOiLkfOuenvh5ZLQD_k-yi7mL1Epr+gGJZ65zr2Fcp2SzE9F7w@mail.gmail.com>
Hi Fabien,
On Tue, Sep 25, 2018, fabien dvlt wrote:
> > ACL Data RX: Handle 13 flags 0x02 dlen 12 #198 [hci0] 21.813116
> L2CAP: Connection Request (0x02) ident 7 len 4
> PSM: 25 (0x0019)
> Source CID: 75
> > HCI Event: Encryption Change (0x08) plen 4 #199 [hci0] 21.813155
> Status: Success (0x00)
> Handle: 13
> Encryption: Enabled with AES-CCM (0x02)
> < ACL Data TX: Handle 13 flags 0x00 dlen 16 #200 [hci0]
> L2CAP: Connection Response (0x03) ident 7 len 8
> Destination CID: 0
> Source CID: 75
> Result: Connection refused - security block (0x0003)
> Status: No further information available (0x0000)
This looks like the well-known race condition for ACL data and HCI
events on USB where the two come through different endpoints. From the
host perspective there's not much we can do since we can't make
assumptions that the connection request was sent over an encrypted
connection if we haven't seen the encryption change request at that
point.
Johan
next prev parent reply other threads:[~2018-09-26 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 16:08 Security block and Bluez - connection issue with Android fabien dvlt
2018-09-26 11:03 ` fabien dvlt
2018-09-26 11:23 ` Luiz Augusto von Dentz
2018-09-26 11:28 ` Johan Hedberg [this message]
2018-10-03 14:20 ` fabien dvlt
2018-12-11 17:12 ` fabien dvlt
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=20180926112801.GA8013@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=fabiendvlt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).