Bluetooth link keys extraction tool

iwanders / README.md

When multibooting Windows and Ubuntu you continuously have to repair your Bluetooth devices in order to use them. This is because during the pairing process the link-key is created. This key is to be associated with a specific MAC adress. This causes problems as the Bluetooth stack in Ubuntu and Windows have separate keys but use the same MAC adress (same bluetooth hardware to communicate to the device).

In my case this caused a Bluetooth-enabled headphone to be either paired with Windows or with Ubuntu. But never with both at the same time.

If the same key were to be used in both operating systems this problem can be solved. If the standard Windows Bluetooth Stack is used a description is here: finding-bluetooth-link-key-in-windows-7-to-double-pair-a-device-on-dualboot-com.

For the said headphone I am required to use the ‘Toshiba Bluetooth Stack’ to get A2DP working in Windows 7. In that system the keys are not stored in the registry, instead they can be found in the following file:

C:\Users\%USERNAME%\AppData\Local\Toshiba\BluetoothStack\V1.0\SDP#####.sdb 

Where the ###### is replaced by an incrementing number for each boot/pair? I have only tested this while paired with one device, but the key is located after the device name at position 0x910 in my case:

$ hexdump -C SDP00025.sdb 00000000 2a 54 6f 73 42 74 53 44 44 42 2a 00 00 00 00 00 |*TosBtSDDB*. | 00000010 01 00 50 9d 83 94 0e 68 d2 01 30 12 00 00 00 00 |..P. h..0. | 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |. | * 00000080 7e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |~. | 00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |. | * 00000800 00 00 00 00 36 04 00 00 36 04 00 00 00 16 94 1a |. 6. 6. | 00000810 57 46 04 04 24 00 50 58 43 20 35 35 30 00 00 00 |WF..$.PXC 550. | 00000820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |. | * 00000910 6d 49 0b 42 66 e8 b1 7f ad 5d 6c 4b a0 5f 10 aa |mI.Bf. ]lK._..| 00000920 30 f5 13 3e 0b 68 d2 01 20 3f 9e 6f 06 68 d2 01 |0..>.h.. ?.o.h..| 

The relevant key is 6d 49 0b 42 66 e8 b1 7f ad 5d 6c 4b a0 5f 10 aa for the device by the name PXC 550 . The aforementioned link provides explanation on where to place this key for Ubuntu to use. Remember to use service bluetooth restart to restart the entire Bluetooth stack, just changing the linkkey file is not enough, a reload is required.

Источник

Finding Bluetooth link key in Windows 7, to double pair a device on dualboot computer

How can I dig up the Bluetooth link key for a paired device in Windows 7? Is this something that is dependent on the Bluetooth stack I’m using (Toshiba), or is there a generic place to store these in Windows 7? Note: I’m not talking about the six-digit code usually typed by the user during pairing — that is worthless since it’s discarded after pairing process. What I mean is the 128-bit link key that the devices exchange during pairing, and use thereafter to encrypt all their Bluetooth traffic. Background: I dualboot Windows 7 / Ubuntu on my laptop, and I would like to have my phone paired to both OS’s. Since the dualbooting computer has only one Bluetooth adapter and thus only one Bluetooth address, I cannot do two pairings to the phone, since on the second pairing (Windows) the phone just replaces the previous pairing (Linux) to the same Bluetooth address. A thread on Ubuntu forums pointed me to what I have to do — pair first on Linux, then on Windows, and then replace the link key on Linux side with the one Windows negotiated. I can find the Linux side pairing key from /var/lib/Bluetooth/[BD_ADDR]/linkkeys — no problems there. However, on Windows side I can’t find the key. According to the forum post, on Windows side the key should be in SYSTEM\ControlSet002\services\BTHPORT\Parameters\Keys\[BD_ADDR] but while that registry key does exist, it has no subkeys. (And a similar registry path in ControlSet001 didn’t have any subkeys either.) One thing I’ve been instructed to do is to capture all events during pairing with Sysinternals Process Monitor. I did this, but I haven’t been able to find any useful information from the captured events, not even by exporting the data to a huge XML and grepping that with the BD_ADDRs (with or without colons). So how could I find the link key for a paired device in Windows 7? Some reference information: Wikipedia: Bluetooth, Security Now: Bluetooth security

5 Answers 5

The registry key you should use is :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys .

On my computer, it refused to let me access this key. I had to change the owner to Administrators before I could see the sub-key.

If you are using the Toshiba Bluetooth stack, its keys are stored somewhere else. One can either find where, or simply return to the Microsoft stack. In the later case, the Bluetooth keys will be stored in the registry as above.

This thread describes the process :

1. Uninstall Toshiba Bluetooth (Add/Remove programs),
2. Reboot,
3. Windows should now detect the «new» Bluetooth device and install its own drivers for it.

Caution: Create a system restore point first, and ensure you have the installation media for the Toshiba driver for going back (just in case). Test well the functionality of the paired phone before crying victory.

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

LKX: Bluetooth Link-Key eXtractor for Android

License

aagallag/Bluetooth-Link-Key-eXtractor

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

LKX: Bluetooth-Link-Key-eXtractor for Android

This is a free, open-source project. I hacked this app up in an evening, so there is likely to be bugs. If you encounter any issues, I would appreciate if you would file an issue at the link below and mention what device you encountered the bug on. Feature requests are welcome too!

Download the app from the Play Store or the GitHub repo.

Simply import the project into Android Studio.

LKX - Bluetooth Link-Key eXtractor Copyright (C) 2016 Aaron Gallagher This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. Contact: Aaron Gallagher

About

LKX: Bluetooth Link-Key eXtractor for Android

Источник

LKX — BT Link-Key eXtractor

LKX — BT Link-Key eXtractor is a app for Android, It’s developed by aagallag author.
First released on google play in 6 years ago and latest version released in 6 years ago.
This app has 0 download times on Google play and rated as 1.00 stars with 2 rated times.
This product is an app in Tools category. More infomartion of LKX — BT Link-Key eXtractor on google play

LKX — Bluetooth Link-Key eXtractor (requires root)

This is a free, open-source project. I hacked this app up in an evening, so there is likely to be bugs. If you encounter any issues, I would appreciate if you would file an issue at the link below and mention what device you encountered the bug on. Feature requests are welcome too!

Source Code:
https://github.com/aagallag/Bluetooth-Link-Key-eXtractor/

License Info:
LKX — Bluetooth Link-Key eXtractor Copyright (C) 2016 Aaron Gallagher

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see .

Источник

LKX — BT Link-Key eXtractor

LKX — Bluetooth Link-Key eXtractor (requires root)100% Free!100% Open-source!

App info

App description

Android application LKX — BT Link-Key eXtractor developed by aagallag is listed under category Tools. The current version is 1.0, updated on 12/08/2016 . According to Google Play LKX — BT Link-Key eXtractor achieved more than 10 installs. LKX — BT Link-Key eXtractor currently has 2 reviews with average vote value 1.0

LKX — Bluetooth Link-Key eXtractor (requires root)

This is a free, open-source project. I hacked this app up in an evening, so there is likely to be bugs. If you encounter any issues, I would appreciate if you would file an issue at the link below and mention what device you encountered the bug on. Feature requests are welcome too!

License Info:
LKX — Bluetooth Link-Key eXtractor Copyright (C) 2016 Aaron Gallagher

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see .

We are currently offering version 1.0. This is our latest, most optimized version. It is suitable for many different devices. Free download directly apk from the Google Play Store or other versions we’re hosting. Moreover, you can download without registration and no login required.

We have more than 2000+ available devices for Samsung, Xiaomi, Huawei, Oppo, Vivo, Motorola, LG, Google, OnePlus, Sony, Tablet . with so many options, it’s easy for you to choose games or software that fit your device.

It can come in handy if there are any country restrictions or any restrictions from the side of your device on the Google App Store.

Источник