Closed pentagramz closed 6 years ago
Command used ubertooth-btle -f -A 38 -tBD ADDR -r 15.pcapng
channels tried changing to 37, 38 , 39
At least for one of the errors you see: It seems like your BLE device uses Bluetooth 4.2's Secure Connections feature. There is currently no known flaw in the involved protocols that would allow you to crack the encryption key. The device is resistant to cracking for now.
Steps to reproduce
Unpair the watch and phone
Start sniff
Start pairing
Capture BLE traffic
5.Once watch restore done...wait for some time
Then unpair the devices
Analyse the captured traffic using crackle
Expected behaviour
I am not able to see conne_req..please help unable to crack key
Actual behaviour
Tell us what happens instead
Instead it shows unable to crack Please see screenshots
Version information
Operating system: Host machine Windows 7 64 bit, running VMware player Ubertooth one connected to VMware , and using inbuilt bluetooth adapter Running commands in lubuntu machine running in VMWare player
Ubertooth tools version (ubertooth-rx -V):
libubertooth 1.0 (2017-03-R2), libbtbb 1.0 (2017-03-R2)
libbtbb version: libbtbb 1.0 (2017-03-R2)
Ubertooth firmware version (ubertooth-util -v): Firmware version: 2017-03-R2 (API:1.02)
If you are reporting a problem that involves third party software (Wireshark/Kismet/etc), please report the version here.
Output