Bug 1459450 - Bluetooth keyboard for LUKS password
Bluetooth keyboard for LUKS password
Status: NEW
Product: Fedora
Classification: Fedora
Component: luks-tools (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-06-07 04:06 EDT by Gurenko Alex
Modified: 2017-06-07 04:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gurenko Alex 2017-06-07 04:06:11 EDT
Description of problem: I'm not sure which component to pick for that, so please fix that accordingly.

 The problem I have is that I'm using a Bluetooth keyboard (Microsoft Surface Ergonomic Keyboard) and my ssd is encrypted with luks. At a boot time when passphrase is prompted, I cannot type password since Bluetooth is not available at this point yet. I've tried to search for ways to add Bluetooth support to initramfs, but still couldn't do it. While my wireless headphones do say that they are connected at luks prompt (I have no way of checking whether it's true) keyboard does not. Is there a way to add a proper Bluetooth keyboard support for that? This will save a lot of trouble for me.

Version-Release number of selected component (if applicable):

How reproducible: 100%

Steps to Reproduce:
1. Boot laptop
2. Wait for LUKS passphrase prompt
3. Try typing a password

Actual results: Cannot type password, since keyboard is not connected

Expected results: Typing password successfully with Bluetooth keyboard

Additional info: I think since Bluetooth keyboards are becoming more popular thanks to big companies, it will be useful to have at least an official/semi-official docs on how to achieve that.

Note You need to log in before you can comment on or make changes to this bug.