On Thu, Jun 11, 2015 at 5:47 AM, Ancor Gonzalez Sosa
YaST2-Security, the YaST module to configure local security settings, is aging. There is a quite deep analysis about the problems here https://docs.google.com/document/d/1BFVou4YrRoc4vPCkofs-Qo2C9b-lWIbuMBiGk3Oc...
The plan described in the document is a mid-term goal. In the short term (next week), the goal is to do less disruptive changes. To be concrete, just:
- Remove any reference to runlevels - Update the list of security settings (currently "home workstation", "networked worstation" and "network server") - Update the list of mandatory services (it will still be independent of the security setting for the time being) - Update the list of extra allowed services (same as above)
- systemd-dmevented
Where that comes from.. ? there is no such systemd component.
- systemd-udevd - systemd-logind - dbus-daemon
- rsyslogd
Rsyslog is not mandatory, the system can run journal only.
- polkitd
Policy kit is started as necessary by the services that require it.
- cron - SuSEfirewall - auditd
New list of extra (harmless) services: - wickedd - nscd - postfix
- ntpd
systemd-timesyncd...
- sshd - haveged
I think your are heading to the wrong direction.. Mostly because you are thinking about updating the module in question to a world that no longer exists...services are not static..they may be activated on demand, by hardware that's plugged in or even by changes in the filesystem, they might be mandatory or optional ..using this list-based approach will cause an endless maintenance pain.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org