Bug 2267051
| Summary: | Bluetooth related Issue using passkey with ones mobile phone | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | fedora-account |
| Component: | bluez | Assignee: | Gopal krishna tiwari <gopalkrishna.tiwari> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 39 | CC: | davidlr, dwmw2, einfjonas, gopalkrishna.tiwari, liblit, pbrobinson, spacewar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-11-27 23:05:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
fedora-account
2024-02-29 12:30:06 UTC
Please report: * Your kernel (uname -a) * Your bluetooth HW (lsusb|grep -i blue) * linux-firmware version (rpm -q linux-firmware) Also I have no idea what passkey is and how it's actually supposed to work so please provide links to documentation on how it's supposed to work with a computer, is it purely camera/QR code based, or does it actually use bluetooth with that as a communications medium. kernel: 6.7.3-200.fc39.x86_64 Bluetooth HW: Bus 003 Device 007: ID 8087:0026 Intel Corp. AX201 Bluetooth firmware: linux-firmware-20240220-1.fc39.noarch (My laptop is Lenovo Thinkpad T14) If you don't have knowledge of the passkeys concept, then a very layman type introduction at https://passkeys.io If your question on how passkeys are actually supposed to work, I think this is a good technical explanation on it and how bluetoorh is involved https://www.corbado.com/blog/webauthn-passkey-qr-code I suggest reading if not the whole, at least most of it. Though I give you a spoiler: From what I read (and understood) about the article, I think the issue boils down to chapter 5: ------------- Start Quote ------------- 5. Passkeys: Bluetooth (caBLE) Besides, the QR code scanning process, there is also the proximity check via Bluetooth (caBLE). Being sure that the client and authenticator are physically close to each other is one of the major benefits of the WebAuthn protocol. More insights on the inner workings of this process are described in the following: ------------- End Quote ------------- That is to say, the proximity check doesn't function or does not get initiated properly unless I first turn of the phone's BT, then turn it back on and have some BT magic happen by getting the phone to discover airpods (wireless headset by apple.) I tried also with setting phone bt off, then back on but this time phone paired with "regular" BT speaker. That didn't provide similar results as with airpods. Instead, the authentication session was still stuck. Thank you for your effort on looking at this (most likely) complicated item. > 5. Passkeys: Bluetooth (caBLE) > Besides, the QR code scanning process, there is also the proximity check via > Bluetooth (caBLE). Being sure that the client and authenticator are So that tells me it's likely BLE (Bluetooth Low Energy) > (wireless headset by apple.) I tried also with setting phone bt off, then > back on but this time phone paired with "regular" BT speaker. That didn't > provide similar results as with airpods. Instead, the authentication session The airpods I believe are BLE and the "regular" speaker likely not so possibly some issue around switching modes. This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. Hello everyone. This is still reproducible for me with Fedora KDE 42. Was not very easy to get to the root of that problem because there is no user dialog why it's not working. Is it possible to get this bug reopened? Thank you! Smartphone: iPhone 16 with iOS 18.6.2 Linux fedora 6.15.10-200.fc42.x86_64 Intel Corp. AX211 Bluetooth linux-firmware-20250808-1.fc42.noarch System Version: ThinkPad E14 Gen 7 Still reproducible in Fedora Gnome 43 6.18.13-200.fc43.x86_64 Intel AX211 linux-firmware-20260221-1.fc43 |