Allow installation with crypted root FS #308
Open
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
|
I don't know for how many people this feature is important. Please rebase the branch to the latest devel tree, I would like to test it first.... |
|
Rebased to devel |
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.
Description
Nowadays I don't trust any storage device anymore to keep my data when I need it, and to delete the data when I don't need/want it anymore. Consequentöy encrypting everything at rest is a maxime of today. do not write any unencrypted data to a storage device.
This PR allows to install your machine with centos/rhel on a crypted root filesystem which can be unlocked on boot via SSH
This PR is based on #307 .
The whole process to install is a bit fiddly, especially as the unlocking needs some workarounds to be automated.
The PR pulls in the epel repositories for dropbear to have an sshd in the initramfs and the copr repository:
uriesk/dracut-crypt-sshthe code just plumbs everything together
Note: the initial setup is still considered unsafe because the passphrase gets transfered via plaintext file into the rescue system. Thats why it will initially will setup a simple default key for the
installimageinstaller.After the reboots are finished the code will change the passphrase by adding the final one and deleting the initial one.
Thats the reason why the initial passphrase is stored unencrypted.