FS#54212 - [rkhunter] Change configuration to use systemd daemon paths
Attached to Project:
Community Packages
Opened by Splith (splith) - Sunday, 28 May 2017, 14:49 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 September 2023, 10:20 GMT
Opened by Splith (splith) - Sunday, 28 May 2017, 14:49 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 September 2023, 10:20 GMT
|
Details
Description: rkhunter by default checks the /etc/init.d path
for startup daemons which hasn't existed for a long time in
arch due to using systemd. Thus it doesn't scan the startup
daemones. There is a post on
https://sourceforge.net/p/rkhunter/mailman/message/34653773/
describing how to fix this, basically by adding this to
/etc/rkhunter.conf
STARTUP_PATHS=/etc/profile /etc/profile.d /etc/systemd/system I think this change should be made to the package so that by default it scans the systemd daemons. Additional info: Package version(s): 1.4.2-2 Steps to reproduce: Install rkhunter and run a test, it will skip the startup daemon test due to not being an init-based system. |
This task depends upon
Closed by Jelle van der Waa (jelly)
Sunday, 03 September 2023, 10:20 GMT
Reason for closing: Upstream
Sunday, 03 September 2023, 10:20 GMT
Reason for closing: Upstream
Comment by Ivy Foster (escondida) -
Thursday, 10 October 2019, 22:45 GMT
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
Since Arch doesn't change upstream's defaults, it seems as though
this is something that should be fixed upstream, and in the
meantime documented on the [rkhunter wiki
page](https://wiki.archlinux.org/index.php/Rkhunter). splith,
would you care to do the honors on the wiki documentation?
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.