• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Watchdog Meldungen bzgl. Hash-werte

A

adato

Guest
Hallo,

zwei Nachfragen an SWSoft blieben bisher unbeantwortet, daher versuche ich es hier einmal.

Wir haben hier Plesk in der Version 8.1 auf Red Hat EL 4 im Einsatz.

Beim Prüfen mit "Watchdog" bekamen ich folgende Meldung (Ausschnitt):

Performing 'known good' check...
/bin/cat [ BAD ]
/bin/chmod [ BAD ]
/bin/chown [ BAD ]
/bin/date [ BAD ]
/bin/dmesg [ BAD ]
/bin/env [ BAD ]
/bin/grep [ BAD ]
/bin/kill [ BAD ]
/bin/login [ BAD ]
/bin/ls [ BAD ]
/bin/more [ BAD ]
/bin/mount [ BAD ]
/bin/netstat [ BAD ]
/bin/ps [ BAD ]
/bin/su [ BAD ]
/sbin/chkconfig [ BAD ]
/sbin/ifconfig [ BAD ]
/sbin/sysctl [ BAD ]
/sbin/syslogd [ BAD ]
/usr/bin/chattr [ BAD ]
/usr/bin/du [ BAD ]
/usr/bin/file [ BAD ]
/usr/bin/find [ BAD ]
/usr/bin/head [ BAD ]
/usr/bin/killall [ BAD ]
/usr/bin/lsattr [ BAD ]
/usr/bin/md5sum [ BAD ]
/usr/bin/pstree [ BAD ]
/usr/bin/sha1sum [ BAD ]
/usr/bin/stat [ BAD ]
/usr/bin/strings [ BAD ]
/usr/bin/top [ BAD ]
/usr/bin/users [ BAD ]
/usr/bin/vmstat [ BAD ]
/usr/bin/w [ BAD ]
/usr/bin/watch [ BAD ]
/usr/bin/wc [ BAD ]
/usr/bin/whereis [ BAD ]
/usr/bin/who [ BAD ]
/usr/bin/whoami [ BAD ]
/usr/sbin/xinetd [ BAD ]

Bei einem zweiten Server war die Meldung identisch. Gibt es einen Grund zur Besorgnis, oder ist die Abweichung der Hash-Werte durch Betriebssystem-Updates begründet?

Danke im voraus!
 
Back
Top