On Sat, Jun 22, 2019 at 08:21:07PM +0200, Marcel Holtmann wrote:
> Hi Sasha,
>
> > [This is an automated email]
> >
> > This commit has been processed because it contains a "Fixes:" tag,
> > fixing commit: d5bb334a8e17 Bluetooth: Align minimum encryption key size
> > for LE and BR/EDR connection
Hi Sasha,
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: d5bb334a8e17 Bluetooth: Align minimum encryption key size for
> LE and BR/EDR connections.
>
> The bot has tested the following trees: v5.1.12, v4.19.53, v4.14.128,
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d5bb334a8e17 Bluetooth: Align minimum encryption key size for LE
and BR/EDR connections.
The bot has tested the following trees: v5.1.12, v4.19.53, v4.14.128, v4.9.182,
v4.4.182.
When trying to align the minimum encryption key size requirement for
Bluetooth connections, it turns out doing this in a central location
in the HCI connection handling code is not possible.
Original Bluetooth version up to 2.0 used a security model where the
L2CAP service would enforce authentica
4 matches
Mail list logo
