From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Alexandre Pereira Nunes <alexandre.nunes@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: After kernel update: connect/disconnect forever while attempting to auto-reconnect
Date: Sun, 19 May 2019 11:39:46 +0300 [thread overview]
Message-ID: <CABBYNZLX+XZG694s+E-L=+VjosbMvytB3nAaVorpghCK=ineSg@mail.gmail.com> (raw)
In-Reply-To: <0FBE6EB8-B42A-4D24-ACAB-80AB47316B97@gmail.com>
Hi Johan,
+Marcel
On Sat, May 18, 2019 at 9:08 PM Johan Hedberg <johan.hedberg@gmail.com> wrote:
>
> Hi Luiz,
>
> On 18 May 2019, at 19.30, Luiz Augusto von Dentz <luiz.dentz@gmail.com> wrote:
> > The problem seems to be here:
> >
> > < ACL Data TX: Handle 512 flags 0x00 dlen 16 #87 [hci0] 9.952984
> > L2CAP: Connection Response (0x03) ident 1 len 8
> > Destination CID: 0
> > Source CID: 65
> > Result: Connection refused - security block (0x0003)
> > Status: No further information available (0x0000)
> >
> > Ruling out encryption since HID don't require it:
>
> When both devices support SSP, encryption is required for any non-SDP PSM. The kernel enforces this regardless of what kind of options were set for the socket.
Perhaps it could be this one:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/net/bluetooth/hci_conn.c?id=d5bb334a8e171b262e48f378bd2096c0ea458265
It looks like the test you mentioned it is just above the check for
enc_key_size, though people mentioned it has been working so could it
be that SSP is not enabled after all?
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2019-05-19 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 5:59 After kernel update: connect/disconnect forever while attempting to auto-reconnect Carlos Pita
2019-05-17 21:39 ` Alexandre Pereira Nunes
2019-05-18 5:33 ` Luiz Augusto von Dentz
2019-05-18 8:53 ` Carlos Pita
2019-05-18 14:08 ` Alexandre Pereira Nunes
2019-05-18 16:30 ` Luiz Augusto von Dentz
2019-05-18 18:08 ` Johan Hedberg
2019-05-19 8:39 ` Luiz Augusto von Dentz [this message]
2019-05-18 17:05 ` Johan Hedberg
2019-05-18 17:09 ` Johan Hedberg
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='CABBYNZLX+XZG694s+E-L=+VjosbMvytB3nAaVorpghCK=ineSg@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=alexandre.nunes@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).