Closed shundhammer closed 1 year ago
Until now, the SecuritySettings instance was created at the proposal summary step or by AutoYaST when it was needed and after the users configuration was already done. But since we added security policies support (STIG) this is different and it is evaluated too early mainly because it also create and instance of SecuritySettings during the initialization instead of doing it using a lazy load init.
We already have a propose_lsm_config as part of the initialization, maybe we should move that proposal and the ssh config proposal to a propose method which will be called when it is really needed storing that the propose is already done just to avoid resetting it like:
def propose!
return if @propose
propose_lsm_config
propose_ssh_config
@propose = true
end
The other options is fix the initialization of the SecurityPolicies::TargetConfig moving the @security accessor to a method
This is superseded by a new PR.
New PR: #1090