linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: John Klug <ski.brimson@gmail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Security block and Bluez 5.47
Date: Wed, 15 Nov 2017 16:09:10 +0200	[thread overview]
Message-ID: <20171115140910.GA19963@x1c.lan> (raw)
In-Reply-To: <CABBYNZJKYniLeC3oGn7QgDyVN27VzjY2g=oeauHkQGSqAUfK+w@mail.gmail.com>

Hi Luiz,

On Wed, Nov 15, 2017, Luiz Augusto von Dentz wrote:
> > Frequently when I connect my Android phone to my bluez 5.47 device I
> > see (btmon):
> >
> >  > HCI Event: Number of Completed Packets (0x13) plen 5
> >
> >                                                             #36 [hci0]
> > 5.709020
> >          Num handles: 1
> >          Handle: 1
> >          Count: 1
> >  < ACL Data TX: Handle 1 flags 0x00 dlen 16
> >
> >                                                             #37 [hci0]
> > 5.714589
> >        L2CAP: Connection Response (0x03) ident 4 len 8
> >          Destination CID: 64
> >          Source CID: 81
> >          Result: Connection refused - security block (0x0003)
> >          Status: No further information available (0x0000)
> >
> > This is using connecting from Android 7 to Bluez 5.47.
> 
> I think this might be due to not having a default agent set which is
> needed if the devices is not trusted so it would require agent
> authorization.

It could also be the USB HCI race between ACL data and HCI events. It's
hard to say for sure though since the complete HCI log was not provided.

Johan

      reply	other threads:[~2017-11-15 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 21:45 Security block and Bluez 5.47 John Klug
2017-11-15 11:39 ` Luiz Augusto von Dentz
2017-11-15 14:09   ` Johan Hedberg [this message]

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=20171115140910.GA19963@x1c.lan \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=ski.brimson@gmail.com \
    /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).