LUKS2 and systemd-boot can be set by the user for the proposal #1109
Conversation
in the Configuration dialog.
|
I'm not sure whether we want to use the configuration screen to throw all kind of experiments there. Have you considered using a role with its own client? I know this doesn't fix exactly in the definition of a role, but since the role allows you to modify most of the settings and allows you to write your own client in which you can ask the user whatever you want or present any information I would feel more comfortable with that, as a testing mechanism. Check for example the Common Criteria dialog. |
| if Yast::UI.QueryWidget(Id(:frame), :Value) | ||
| # pbkdf2 is default because it can be used by grub2 too | ||
| proposal_section["encryption"] = { "type" => "luks2", "pbkdf" => "argon2id", | ||
| "password" => Yast::UI.QueryWidget(Id(:pw1), :Value) } |
There was a problem hiding this comment.
I fear storing the password in plain text as part of ProductFeatures may result in password leak in the YaST logs.
There was a problem hiding this comment.
Yes, you are right. I have seen how you have fixed this problem:
yast/system-role-common-criteria@feb23e6
|
It is obsolete. Closing |
in the Configuration dialog:
jsc#PED-1906
Screenshots
Other associated PRs :
yast/yast-installation-control#125
yast/yast-bootloader#694
yast/yast-storage-ng#1370