• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

rkhunter config problem

T

TobiasP

Regular Pleskian
When trying to run rkhunter manually I get the error:
"Installation directory does not exist: /opt/psa"
I haven't changed the install directory setting in the rkhunter config file.

Could you someone send me the "default" rkhunter config file?
Or tell me a way to reset / reinstall rkhunter?
 
rkhunter is a part of psa-watchdog package. Try to reinstall this package.
 
Yes, you can do it with autoinstaller. Just uncheck Watchdog there and then install it back.
 
Thank you that helped.
Updating i18n fails. Log entry:
[11:00:06] Info: Executing download command '/usr/bin/wget -q -O /opt/psa/var/modules/watchdog/lib/rkhunter/lib/rkhunter/tmp/rkhunter.upd.r9MIzDUis4 http://rkhunter.sourceforge.net/1.3/i18n/1.3.4/i18n.ver'
[11:00:06] Checking file i18n versions [ Update failed ]
[11:00:06] Warning: Download of 'i18n.ver' failed: Unable to determine the latest version number.

any ideas?
 
Is there a simple way to update rkhunter in Plesk without buying an extension?

Why does watchdog still have an ancient version still?
 
Yes, there is a "simple" way to upgrade rkhunter... but be aware, that Plesk updates/upgrades/patches may overwrite any of your changes, so please don't blame Parallels, because you changed an integrated extension. ^^


Tutorial to upgrade rkhunter from the integrated Plesk version to the actual version 1.4.2 based on Ubuntu systems :
( Please make sure that the used paths in this tutorial exist on your system, because "/opt/psa/" for example may be "/usr/local/psa/ on your system - change the paths to YOUR system environment to make this work as expected !!! )​

  • Preparation, download, untar :
Code: 
mkdir -p /root/addons/rkhunter
cd /root/addons/rkhunter
wget http://jaist.dl.sourceforge.net/project/rkhunter/rkhunter/1.4.2/rkhunter-1.4.2.tar.gz
tar -zxvf rkhunter-1.4.2.tar.gz
cd rkhunter-1.4.2

mkdir /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2
  • Control what is going to be installed, install rkhunter 1.4.2 and modify the permissions :
Code: 
./installer.sh --layout custom /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2 --striproot /opt/psa --install --show

./installer.sh --layout custom /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2 --striproot /opt/psa --install

chown -hR root:psaadm /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2
  • Make some backups and move/copy/rsync files and folders :
Code: 
mv /opt/psa/etc/modules/watchdog/rkhunter.conf /opt/psa/etc/modules/watchdog/rkhunter.conf.backup
cp /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/etc/rkhunter.conf /opt/psa/etc/modules/watchdog/rkhunter.conf

mv /opt/psa/admin/sbin/modules/watchdog/rkhunter /opt/psa/admin/sbin/modules/watchdog/rkhunter.backup
cp /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/bin/rkhunter /opt/psa/admin/sbin/modules/watchdog/rkhunter


rsync -r /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/lib64/rkhunter/scripts/* /opt/psa/var/modules/watchdog/lib/rkhunter/rkhunter/scripts
rsync -r /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/var/lib/rkhunter/db/* /opt/psa/var/modules/watchdog/lib/rkhunter/lib/rkhunter/db
rsync -r /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/var/lib/rkhunter/tmp/* /opt/psa/var/modules/watchdog/lib/rkhunter/lib/rkhunter/tmp

rsync -r /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/share/doc/* /opt/psa/var/modules/watchdog/lib/rkhunter/doc
rsync -r /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2/share/man/* /opt/psa/var/modules/watchdog/lib/rkhunter/man

  • Edit "/opt/psa/etc/modules/watchdog/rkhunter.conf" :
...and use the example configuration, based on the standard Plesk integrated rkhunter.conf, attached as TXT ( rkhunter.conf.example.Ubuntu.txt ), here in the post.​

  • While you are still on your command line, please update rkhunter now, to be sure, that your version is up-to-date :
Code: 
/opt/psa/admin/bin/modules/watchdog/rkhunter --update --configfile /opt/psa/etc/modules/watchdog/rkhunter.conf

  • Please use the command "/opt/psa/admin/bin/modules/watchdog/rkhunter --help" for descriptions to additional commands for rkhunter.
 

Attachments

  • rkhunter.conf.example.Ubuntu.txt
    44.8 KB · Views: 52
This is for install and not update. There is more to it than this as the old version would have to be removed first.

Also, I am on Centos, not Ubunto. :)
 
Hi Richieboydev,

are you serious with your post? o_O

Yes this IS written for Ubuntu, but if you would have had a closer look, then you would have seen, that you just have to change "/opt/psa/" to "/usr/local/psa/" - I think this might even be possible, with only a few linux knowledge. The command "locate rkhunter" on your system would as well show you the paths, where Plesk installed the integrated version and you could then see as well, which part from the "Ubuntu tutorial" might need a change.

Btw.... the installation from rkhunter in the way it is described, is a "custom" installation, which means there are no other folders on your system being used. You could verify this as well with the command "./installer.sh --layout custom /opt/psa/var/modules/watchdog/lib/rkhunter-1.4.2 --striproot /opt/psa --install --show". Using the tutorial, you would as well see, that nearly all files of a previous Plesk-integrated-version will get overwritten with the steps - and even backuped. There is no "upgrade" - possibilty, so this way is the most recommended one, if you would like to use the current rkhunter version 1.4.2 instead of the Plesk integrated one.


If you would like an individual "CentOS" tutorial, because you don't want to change the described paths by yourself, I would recommend to order a Plesk Support ticket at Parallels - Support . :)
 
I do not mind changing the paths.

What I meant about removing the old version is that it will most likely be reinstalled during some Plesk updates. I am afraid this will cause issues.

It may be a better solution to remove Watchdog completely and reinstall with out Plesk and then install this version. What do you think?

Also, in terms of this old version I know it shows some false positives but is it vulnerable at all?
 
Hi Richieboydev,

no... rkhunter is not vulnerable - you just can't update any new, updated language files in version 1.3.4 ( i18n ) - the other files are still updated, as you can see in your logs.

And as well "no"... it doesn't show any false positiv... you just should configure it to YOUR needs. The config file needs adjustement on every linux system when you use rkhunter, because paths, whitelists and scripts have to be configured, so that rkhunter doesn't warn about something that, without any definition, might being declared as a potential risk. The standard Plesk - pre-configuration is based on the standard vendor's configuration, where only a minimum is modified - some software need a documentation to understand the correct usage, please be so kind to read the one from rkhunter to modify your settings to your very own system configurations.

And no.... the "old" version will not "automatically" being re-installed... this as well depends on your very own Plesk usage. I prefer reading the changelogs, BEFORE I update/upgrade/patch a server, just to be sure, that I really want it. Maybe you should consider to switch of Plesk-auto-updates and try to follow my behaviour, if you would like to be sure, that YOUR changes still exist tomorrow. ^^
 
Hi, I followed the instruction of UFHH01 setp by step. I'm able to start the "watchdog" in Plesk and it shows me the new version of rkhunter:
Code: 
[ Rootkit Hunter version 1.4.2 ]
rkhunter seems to check the system. But the status bar in Plesk remains at 0% (ok, never mind). Finally, after all tests finished, Plesk shows the state "never checked". I even get a mail, but in this mail the only content is "Please inspect this machine, because it may be infected.". No log file as it was before upgrading rkhunter. Because of the status bar at 0% and the missing log file in the mail I suppose rkhunter can't find the logfile?

I checked all files and permissions. Seems OK. Can anyone help me? Thank you.
 
Hello,

I want to bump this post because I have the same issue. I posted this Long time ago in another thgread but I cannot find it.

I found out that the logfile is shown during the scan if you press the refresh-button. But it disappears if the scan is finished. Looking at the source-code of the site you find that there is the complete logfile inside but embedded in a a table wich is marked hidden.

So there is a condition wich lets it be hidden. Wich one and how can I prevent it?
 
You must log in or register to reply here.

Similar threads

C
Question Strategic questions
Replies
9
Views
1K
mow
M
Linulex
Issue roundcube upgrade fails from 18.0.63 to 18.0.64 when mariadb 10.11.9 is installed
Replies
4
Views
371
Linulex
Linulex
T
ISSUE - Nginx config generation failure and http2 directive implementation failure
Replies
14
Views
2K
Bitpalast
Bitpalast
L
Question Problems with conf-available/javascript-common.conf
Replies
2
Views
644
Larian
L
S
Question How to update vhosts path (not change, update)
Replies
0
Views
317
SDGPete
S
Back
Top