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

Can't pair to both Ubuntu and Windows on the same laptop. #2026

Open
BenBlumer opened this issue Nov 17, 2023 · 5 comments
Open

Can't pair to both Ubuntu and Windows on the same laptop. #2026

BenBlumer opened this issue Nov 17, 2023 · 5 comments

Comments

@BenBlumer
Copy link

BenBlumer commented Nov 17, 2023

I dual boot Ubuntu and Windows 11. I had my keyboard paired with W11 (as well as a phone and a tablet). I then booted in Ubuntu and tried to pair. I was getting authorization failed messages from bluetoothctl. I cleared all the bluetooth profiles. It paired and connected. I then booted W11 and tried to re-pair. It wouldn't do it. This time, I only cleared the profile for the Ubuntu connection. All of a sudden, it would pair.

It seems like ZMK doesn't want to pair to two OSes on the same device (or with the same bluetooth MAC address?).

Is this a fundamental bluetooth issue or a ZMK issue?

Originally posted by @BenBlumer in #1189 (comment)

@ReFil
Copy link
Contributor

ReFil commented Nov 17, 2023

Zmk enforces strict security and won't store multiple keys for the same device, there is a way to do it though
https://hoelter.prose.sh/kinesis-advantage-360-bluetooth-dualboot

@lesshonor
Copy link
Contributor

@caksoylar
Copy link
Contributor

I think it would be good to put a pointer to the wiki (with a short summary) in the docs, under the Bluetooth feature page troubleshooting header.

@BenBlumer
Copy link
Author

Zmk enforces strict security and won't store multiple keys for the same device, there is a way to do it though https://hoelter.prose.sh/kinesis-advantage-360-bluetooth-dualboot

What is the security risk? Genuinely asking.

I can understand preventing a device from pairing itself by saying "Trust me -- we've already paired!". Is that risk not solved by insisting each OS must pair to a different BT profile on the ZMK? That way a user has to explicitly pair the device, as they always do, and we should have the same amount of security we always have.

@piit79
Copy link

piit79 commented Mar 6, 2025

What is the security risk? Genuinely asking.

Does anyone know? I'd love to understand what the supposed security risk is. Having to copy over the pairing keys feels like a significant low-level hassle that a regular user should not have to go through...

Would it be possible to patch this behaviour out, even unofficially? I have no idea at what part of the ZMK source to look at...

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

5 participants