Bug 2184519 - InitramFS Generation with Paired Bluetooth Device Metadata
Summary: InitramFS Generation with Paired Bluetooth Device Metadata
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm-ostree
Version: 37
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-04 21:28 UTC by Alper Kanat
Modified: 2023-04-05 08:30 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-05 08:30:02 UTC
Type: Bug
Embargoed:
me: fedora_prioritized_bug?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-802 0 None None None 2023-04-04 21:29:54 UTC

Description Alper Kanat 2023-04-04 21:28:24 UTC
Description of problem:

An already paired bluetooth device cannot be used to decrypt LUKS during boot.


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

Fedora Silverblue 37


How reproducible: Always


Steps to Reproduce:
1. Encrypt filesystem during installation
2. Pair with a bluetooth device
3. Try to decrypt filesystem with the paired bluetooth device during boot

Actual results:

System cannot pair with the bluetooth device so the filesystem cannot be decrypted.

Expected results:

Already paired bluetooth devices can be used to decrypt filesystem.

Additional info:

I've previously created an issue to rpm-ostree here: https://github.com/coreos/rpm-ostree/issues/4214

Comment 1 Alper Kanat 2023-04-04 21:29:38 UTC
I wanted to get this issue into Bugzilla as I discovered the discussions about the future of encryption on Fedora. Hope the timing is correct :)

Comment 2 Timothée Ravier 2023-04-05 08:30:02 UTC
Thanks for filling this issue.

We track enhancements in Silverblue in https://github.com/fedora-silverblue/issue-tracker so I've created an issue there instead: https://github.com/fedora-silverblue/issue-tracker/issues/447


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