• 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.

rkhunter - security warnings FC2 Plesk8

A

aernative

Guest
System - FC2 - Plesk 8

First off i ran the scanner and got warnings about alow root login and some packages being out of date or un patched.

So far i have got round the root login warning by switching to SSH2 only and switching the permit root to "no" then adding a user for SSH out of the root group using RSH keys to login... that seems to satisfy the scanner...

I am still stuck on how to deal with the following application version warnings -

* Application version scan
- GnuPG 1.2.4 [ Old or patched version ]
- Apache 2.0.51 [ Old or patched version ]
- Bind DNS 9.2.3 [ OK ]
- OpenSSL 0.9.7a [ Old or patched version ]
- PHP 4.3.10 [ Old or patched version ]
- Procmail MTA 3.22 [ OK ]
- ProFTPd 1.2.10 [ OK ]
- OpenSSH 3.6.1p2 [ Old or patched version ]

I have seen posts about the "atomic" packages, however I am not sure what is the best practice to sort this scenero out - do i need to update to FC3/4 (or even 5 now...).
 
Back
Top