Feature added by: Ancor Gonzalez Sosa (ancorgs) Feature #318425, revision 1 Title: Adjust YaST2-Security to systemd Requested by: Ancor Gonzalez Sosa (ancorgs) Partner organization: openSUSE.org Description: Some features of the YaST security module are still based on the concept of runlevel and the services that should be activated for runlevels 3 and 5. The security team should take a look into the existing approach and suggest a new more systemd-compliant way of achieving the same goals, as well as a more up-to-date list of services to be considered basic or extra (using the current nomenclature). Then this new approach should be implemented, removing the currently broken sections from YaST2-Security. References: I can't find them right now. But I remember openSUSE (or was SLE12) reviews mentioning the broken YaST2-Security as annoying. Use Case: Joe wants to wants to get an overview on how secure its system is. He needs an accurate picture in a tool he can feel confident about. Having non-functional parts on the report, refering to concepts that no longer apply, will make him distrust YaST2-Security as a whole. -- openSUSE Feature: https://features.opensuse.org/318425