Bug 2184519

Summary:	InitramFS Generation with Paired Bluetooth Device Metadata
Product:	[Fedora] Fedora	Reporter:	Alper Kanat <me>
Component:	rpm-ostree	Assignee:	Colin Walters <walters>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	amurdaca, dustymabe, jmarrero, jonathan, lucab, miabbott, philip.wyett, travier, walters
Target Milestone:	---	Flags:	me: fedora_prioritized_bug?
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-05 08:30:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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