-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LUKS2 enablement: alternative take #1383
Conversation
92aa6d5
to
8534afd
Compare
sounds good. who can put an official review on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only miss changelog and new version.
Added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
✔️ Internal Jenkins job #1156 successfully finished |
how does the control.xml snippet have to look like for that? |
E.g.:
|
Problem
We have been discussing for some time how to make LUKS2 easily configurable (and the default option) when installing Tumbleweed with YaST.
This relatively old comment summarizes my proposal, which was:
Solution
This pull request implements exactly that. One commit per item.
There are no user-visible changes in the installation workflow or in the Guided Setup. YaST will now simply use LUKS2 and PBKDF2 if configured to do so at control.xml and the user decided to encrypt the system.
The default encryption step at the Expert partitioner now looks like this (for all systems, it does not depend on control.xml).
Testing
I just did some preliminary manual tests of the Partitioner (see screenshot above).