Allow /etc/crypttab to be written with USB keyfiles #2488
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lmouelle
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My attempt to fix the issue here:
#2190
Basically LUKS with keyfiles on a USB drive is busted, selinux is blocking systemd-cryptsetup-generator from accessing /run/var/init so units cannot be generated. Maybe there's a better way to write this policy, I created a module similar to this to bypass the issue in my environment
Pretty obviously wrong and broken for some time (not sure if this is the best target branch since this is impacting existing Fedora releases like IoT 41 and Workstation 41.