Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAELgYhdqAxTGA98RsUEOSEA5WfhxGaVn7C_DegAfU13sHx817A@mail.gmail.com>
 <CANxMttCx4uFeVpM9EsYmfg9VoXG45ihpzw=phJcx0Uy53cGD_A@mail.gmail.com>
 <CABBYNZLGgUL6W=-v+stoaukpN5kvt1AHFBQ_vEdh=sqU9JO0LQ@mail.gmail.com>
 <CAELgYhcCBAUr6oQxTnmjBjQfkc8JeTbkXHea64PN+7cWQSqQ=Q@mail.gmail.com>
 <CANxMttCqEYDZOwTriLqC-q39+JhEJ9KCOsPhRqkjZwE1h-64Gg@mail.gmail.com>
 <CABBYNZKbWAaO9dTnHcV7vCYodRQYEZT8=PBws+=_iip-7Njo2w@mail.gmail.com> <0FBE6EB8-B42A-4D24-ACAB-80AB47316B97@gmail.com>
In-Reply-To: <0FBE6EB8-B42A-4D24-ACAB-80AB47316B97@gmail.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Sun, 19 May 2019 11:39:46 +0300
Message-ID: <CABBYNZLX+XZG694s+E-L=+VjosbMvytB3nAaVorpghCK=ineSg@mail.gmail.com>
Subject: Re: After kernel update: connect/disconnect forever while attempting
 to auto-reconnect
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>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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