lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Feb 2019 13:58:45 +0100
From:   Marcel Holtmann <>
To:     Andrey Smirnov <>
        "Pierre-Loup A . Griffais" <>,
        Florian Dollinger <>,
        Johan Hedberg <>,
Subject: Re: [RFC] Bluetooth: Retry configure request if result is

Hi Andrey,

> Due to:
> - current implementation of l2cap_config_rsp() dropping BT
>   connection if sender of configuration response replied with unknown
>   option failure (Result=0x0003/L2CAP_CONF_UNKNOWN)
> - current implementation of l2cap_build_conf_req() adding
>   L2CAP_CONF_RFC(0x04) option to initial configure request sent by
>   the Linux host.
> devices that do no recongninze L2CAP_CONF_RFC, such as Xbox One S
> controllers, will get stuck in endless connect -> configure ->
> disconnect loop, never connect and be generaly unusable.
> To avoid this problem add code to do the following:
> 1. Store a mask of supported conf option types per connection
> 2. Parse the body of response L2CAP_CONF_UNKNOWN and adjust
>    connection's supported conf option types mask
> 3. Retry configuration step the same way it's done for
> Signed-off-by: Andrey Smirnov <>
> Cc: Pierre-Loup A. Griffais <>
> Cc: Florian Dollinger <>
> Cc: Marcel Holtmann <>
> Cc: Johan Hedberg <>
> Cc:
> Cc:
> ---
> Everyone:
> I marked this as an RFC, since I don't have a lot of experience with
> Bluetooth subsystem and don't have hight degree of confidence about
> choices made in this patch. I do, however, thins is is good enough to
> start a discussion about the problem.

can you take a btmon -w trace.log protocol trace so that I can see where it fails. This seems a really odd behavior of the Xbox controller. We have to be careful in not breaking Bluetooth qualification to just workaround some buggy remote device.



Powered by blists - more mailing lists