Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Due to missing support for preboot ACL user won't be able to get access to any devices connected to TB3 doc on boot time before actually bolt daemon start.

Version-Release number of selected component (if applicable):
bolt-0.4-3.el7

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
The most easiest way how to reproduce is having at least one encrypted partition. When you try to enter the password via external USB keyboard you won't be able to.

Solution upstream targeting version 0.6 - https://gitlab.freedesktop.org/bolt/bolt/issues/77

bolt 0.6 is out[1] and it has support for it.

[1] https://gitlab.freedesktop.org/bolt/bolt/tags/0.6

I have verified that bolt-0.7-1.el7 is installed with RHEL-7.7-20190628.n.1 and also that boot_acl is present in sysfs for certain Thunderbolt chipsets. Connecting and authorizing a Thunderbolt dock added the UUID to the boot_acl file. The rest of the Thunderbolt testing has also been passing. Marking as verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2292