Actions
action #135194
closedEdit validate_encrypt module or create new one
Start date:
2023-09-05
Due date:
% Done:
0%
Estimated time:
Description
Currently, in the module that we use for validating encrypted disks after installation, there are many checks that don't really make sense to keep, as they do not have to do with the settings chosen during installation itself. For example, verifying the LUKS version or the key location, is out of our testing scope.
The particular module is used by other teams (security and qam), so before editing it we could contact them to check if they need the particular checks, or simply create a new one that will validate the disk encryption accordingly, avoiding checks that do not concern Yast team.
Acceptance criteria
- Investigate and select the proper encryption checks.
- Make sure we will not remove checks significant to other teams.
- Replace module and test data in current tests.
Updated by syrianidou_sofia about 1 year ago
- Parent task deleted (
#134615)
Related to failure described in ticket: https://progress.opensuse.org/issues/134615
Updated by tinawang123 about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by tinawang123 about 1 year ago
Updated by tinawang123 about 1 year ago
- Status changed from In Progress to Resolved
Actions