Closed lslezak closed 3 months ago
Questions
- Is this the right approach?
I think it is a valid approach.
- Which devices can be actually encrypted?
All block devices could be encrypted, even logical volumes (Disk, Partition, Md, LvmPv, LvmLv, etc).
- Should we check the encryption status for all kinds of devices or are there some cases where it does not make sense or is not supported? It could save some work for the translators...
In DeviceDescription
there are two "branches": #formatted_device_type_label
and unformatted_device_type_label
. This PR covers the first branch, but I think we should add "Encryption" also in the cases of unformatted devices (e.g., "Encrypted PV of %s").
In
DeviceDescription
there are two "branches":#formatted_device_type_label
andunformatted_device_type_label
. This PR covers the first branch, but I think we should add "Encryption" also in the cases of unformatted devices (e.g., "Encrypted PV of %s").
Yes, this first commit was just a PoC and first I wanted to get the answer for the question about which devices can be encrypted. I'll add it in the following commit(s).
- In YaST it is OK because it has a dedicated column with encryption status
- In Agama we would like to have the status included directly in the label
Just thinking aloud: YaST could benefit from this approach too.
Possibly yes, but that's currently out of scope...
:heavy_check_mark: Internal Jenkins job #1154 successfully finished :heavy_check_mark: Created OBS submit request #1168841
Problem
Solution
Notes
Testing
Screenshots