Test scripts in general about sweyntooth_bluetooth_low_energy_attacks HOT 1 CLOSED

Hi @guillaumeschatz thanks for the feedback

About the link-layer overflow. While we have explained the attack by using the version indication, it was stated that increasing the Link Layer length field is the main requirement. Even if L2CAP is involved, we are changing the Link Layer length which is processed before the L2CAP is processed. Furthermore, L2CAP has its own length field which we are not changing here.

Nevertheless, we will update the link_layer_length_overflow to alternate between sending a malformed version request and pairing request by this weekend and let you know.

We are aware of the LLID deadlock script issues and already fixed it by a recent commit:
https://github.com/Matheus-Garbelini/sweyntooth_bluetooth_low_energy_attacks/blob/master/llid_dealock.py

As for the Zero LTK installation, some peripherals do not support pairing at all. In this case, it's not possible to trigger the Zero LTK installation. To verify if the peripheral you are testing indeed is not supporting pairing you can try to use your smartphone to manually perform a pairing. In android, you can do that by connecting to the peripheral via the Bluetooth system menu.

from sweyntooth_bluetooth_low_energy_attacks.