http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 http://bugzilla.opensuse.org/show_bug.cgi?id=1132919#c2 --- Comment #2 from Dirk Weber --- BTW: the current Tumbleweed package seccheck-3.0-16.1.noarch.rpm (Tumbleweed snapshot 20190428) has the same bug. Additionally: the package description should also be updated as the scripts are no longer started by cron: rpm -q --info -p seccheck-3.0-lp151.4.1.noarch.rpm ... Description : Regularly executable scripts (via cron) for checking the security of your system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 http://bugzilla.opensuse.org/show_bug.cgi?id=1132919#c3 Alexander Bergmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abergmann@suse.com --- Comment #3 from Alexander Bergmann --- Thanks Dirk, I will have a look at this problem and update the description. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 http://bugzilla.opensuse.org/show_bug.cgi?id=1132919#c5 --- Comment #5 from Dirk Weber --- The seccheck package is broken in Tumbleweed ever since it was switched from cron to systemd timers in March 2019. There are several problems with this switch: 1. the timers are not enabled by default and there is no hint that this has to be done by the user/administrator after the distribution update or after package installation. 2. even if the timers are enabled manually they do not work as the systemd timer configurations included in the package are faulty which is the main issue of this bug report. The faulty systemd timer configuration was then taken over to Leap 15.1. The intention of the seccheck package are simple security checks for a system. Users could feel secure when they do not get mail notifications about changes on their system but actually the checks are not executed at all because the timers do not trigger. The bug was reported almost 6 months ago and before the final release of Leap 15.1. This is a security related package and the fix is actually quite simple, even patches are provided within this bug. Submit Request 729253 to include the patches is pending for roughly 1 month. I would really appreciate if there was some progress with this bug even when I already applied workarounds on the systems administrated by me to enable the functionality. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 http://bugzilla.opensuse.org/show_bug.cgi?id=1132919#c7 Dirk Weber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #7 from Dirk Weber --- This bug and bug 985802 were fixed in Tumbleweed with sr 759886 resulting in seccheck-3.0-17.1.noarch which was included in snapshot 20191229. Now this correction needs to be picked up for a maintenance update of Leap 15.1 (and SLE 15 SP1) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 http://bugzilla.opensuse.org/show_bug.cgi?id=1132919#c9 Dirk Weber changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |security-team@suse.de Flags| |needinfo?(security-team@sus | |e.de) --- Comment #9 from Dirk Weber --- openSUSE Leap 15.2 entered Beta phase: https://lists.opensuse.org/opensuse-factory/2020-02/msg00429.html Would be nice if the released version would contain a seccheck package with working systemd timers configurations. This correction and others are available in Tumbleweed for almost 2 months, see comment 7. -- You are receiving this mail because: You are on the CC list for the bug.